Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 11 Jul 2002 02:51:27 +0200
From:      Cyrille Lefevre <cyrille.lefevre@laposte.net>
To:        Mark Valentine <mark@thuvia.demon.co.uk>
Cc:        Dag-Erling Smorgrav <des@ofug.org>, Wes Peters <wes@softweyr.com>, Dan Moschuk <dan@freebsd.org>, arch@freebsd.org
Subject:   Re: Package system flaws?
Message-ID:  <20020711005127.GB82744@gits.dyndns.org>
In-Reply-To: <20020708020907.GB83084@gits.dyndns.org>
References:  <200207071546.g67FkVIL018923@dotar.thuvia.org> <20020708020907.GB83084@gits.dyndns.org>

next in thread | previous in thread | raw e-mail | index | archive | help
message resent due to mta misconfigation.

On Mon, Jul 08, 2002 at 04:09:07AM +0200, Cyrille Lefevre wrote:
> On Sun, Jul 07, 2002 at 04:46:31PM +0100, Mark Valentine wrote:
> [snip]
> > However, the archive members are _not_ the individual files comprising
> > the package.  Instead, the package is split into logical sub-packages
> > (there may be only one, that's fine), such as the core run-time package,
> > language sets, development headers and libraries, end-user documentation.
> > Each sub-package is stored as a compressed archive (.tar.bz2 or whatever).
> > The _package_ archive comprises the package metadata files (optionally
> > compressed - useful for the larger files such as +CONTENTS) and the
> > sub-package(s), each as a package archive member.
> 
> that's exactly what HP-UX packages (depots) are w/ using another level.
> 
> 	BUNDLE.PRODUCT.FILESET
> 
> a bundle may contain one or more products which may contain one or more
> filesets. usually, depot are just in the form of PRODUCT.FILESET where
> PRODUCT is something like `tar' and FILESETS are something like `core',
> `man', `lib', `shlib', `doc', etc. w/ dependencies between them.
> 
> > The idea here is to allow individual access to those parts of the package
> > that are needed individually, whilst gaining the benefits of compressing
> > major portions of the package as collections of files (to which individual
> > access is not generally required).
> > 
> > While the division of an existing port into sub-packages requires effort,
> > it's necessary only to gain the benefits of optionally-installable sub-
> > packages.
> > 
> > For existing ports, and for the majority of ports which will never likely be
> > sub-package, pkg_create simple creates the package archive using the existing
> > metadata files and a single compressed archive of the packages files.
> [snip]
> 
> IMHO, it would be better to provide each sub-package as it's own rather
> to put them all in a single archive. so, you have more granularity on
> what to download. if I just want tar-core and tar-man, I don't have to
> fill my disk w/ tar-doc, etc.
> 
> > The package install tools would allow the user to select between optional
> > sub-packages.  The base sub-package may be marked as "required".  If there
> > are only "required" sub-packages, or the user elects to install "all" or
> > "only required" sub-packages, no dialog is necessary.  And so on..
> 
> last year, I propose to port the SVR4 pkg commands to FreeBSD but no
> one was interrested. so, I give up.

Cyrille.
-- 
Cyrille Lefevre                 mailto:cyrille.lefevre@laposte.net

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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020711005127.GB82744>