From owner-freebsd-arch  Mon Jul  8 11:24:50 2002
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 10B5937B400; Mon,  8 Jul 2002 11:24:47 -0700 (PDT)
Received: from mail2.panix.com (mail2.panix.com [166.84.1.73])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 9BB4A43E42; Mon,  8 Jul 2002 11:24:46 -0700 (PDT)
	(envelope-from rsi@panix.com)
Received: from panix1.panix.com (panix1.panix.com [166.84.1.1])
	by mail2.panix.com (Postfix) with ESMTP
	id 107C5917F; Mon,  8 Jul 2002 14:24:46 -0400 (EDT)
Received: (from rsi@localhost)
	by panix1.panix.com (8.11.3nb1/8.8.8/PanixN1.0) id g68IOko07696;
	Mon, 8 Jul 2002 14:24:46 -0400 (EDT)
Message-Id: <200207081824.g68IOko07696@panix1.panix.com>
X-Authentication-Warning: panix1.panix.com: rsi set sender to rsi@panix.com using -f
To: "Artem Tepponen" <temik@egartech.com>
Cc: "Doug Barton" <DougB@FreeBSD.org>,
	"Garrett Wollman" <wollman@lcs.mit.edu>, <mark@thuvia.demon.co.uk>,
	<arch@FreeBSD.org>
Subject: Re: Package system flaws?
References: <5235EF9BAE6B7F4CB3735789EEF73B2907416F@turtle.egar.egartech.com>
From: Rajappa Iyer <rsi@panix.com>
Date: 08 Jul 2002 14:24:46 -0400
Reply-To: rsi@panix.com
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-arch.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-arch>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-arch>
X-Loop: FreeBSD.ORG

"Artem Tepponen" <temik@egartech.com> writes:

> The only problem is how to handle metadata piece that
> have to have at least two properties:
> 1. It should be available without whole thing being decompressed.
> 2. It should be available asap in case of slow link.

It seems to me that the solution is staring us right in the face.
Currently, the ports mechanism already separates data and metadata.
IMHO, the best solution is to extend the ports mechanism so that it
can be told to fetch and install binaries instead of building it
locally.  IOW, perhaps one additional file per port and some
additional rules in bsd.port.mk.

This seems to me to be the cleanest solution.

Thanks,
Rajappa
-- 
<rsi@panix.com> a.k.a. Rajappa Iyer.
	They also surf who stand in the waves.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message