-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sun, 23 Jan 2000, Hubert Feyrer wrote:

>On Sun, 23 Jan 2000, Jim Wise wrote:
>>     f.) modify pkg_* to understand pkgsets which are tarballs of
>> 	pkgs with a contents file of some sort.  These will be
>> 	used by sysinst to 1.) minimize the number of files to
>> 	be downloaded and 2.) present the current selection
>> 	granularity by default.
>
>If you have any ideas on this, I'd be curious to hear them. :)

At the simplest, a pkgset could be a tarball with the binary package
.tgz's and possibly an +INDEX file of some sort containing a list of
packages in the current set.  Three operations are supported on a pkg
set:

      * install the whole set (tar zxf set_name.tgz *.tgz && pkg_add *)

      * list packages in a set (tar ztf set_name.tgz *.tgz) or (tar zxf
	set_name.tgz +INDEX && cat +INDEX)

      * install a specific pkg from a set (tar zxf set_name.tgz
	pkg_name.tgz && pkg_add pkg_name.tgz).

It is explicitly intended that pkg sets a.) physically contain the
relevant pkgs and b.) do not have dependencies or other mechanics of
their own, but are merely a delivery/bundling mechanism for the (quite
fine) packaging mechanism we already have.

- -- 
				Jim Wise
				jwise@draga.com

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.0i for non-commercial use
Charset: noconv

iQA/AwUBOItxtC2NgFbJL33VEQL4uQCg2P//1ebjafhZn0BX9VFlLEfeSs8An38E
SAezlQuh0TyO+Vh29eQuE1HB
=cx/0
-----END PGP SIGNATURE-----