Date: Thu, 8 Aug 2002 20:28:30 -0400 From: The Anarcat <anarcat@anarcat.ath.cx> To: Max Okumoto <okumoto@ucsd.edu> Cc: libh@FreeBSD.ORG Subject: Re: package format and creation Message-ID: <20020809002829.GA20585@dojo> In-Reply-To: <hfu1m5td5j.fsf@multivac.sdsc.edu> References: <7F90C363-AA43-11D6-9D65-0050E4A0BB3F@anarcat.ath.cx> <hf8z3idxua.fsf@multivac.sdsc.edu> <20020808141445.GA24117@lenny.anarcat.ath.cx> <hfu1m5td5j.fsf@multivac.sdsc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Thu, 08 Aug 2002, Max Okumoto wrote: > The Anarcat <anarcat@anarcat.ath.cx> writes: [...] > > libh is, for me, 2 things: > > > > - console or Graphical UI > > - package library > > > > the rest is extensions, and we must not focus on those yet. Those > > extensions will have to be written for seperate package configurators > > (e.g. the "net" package configurator or "apache" configurator, etc). > > When you say extension do you mean? > libh/lib/fooext + libh/release/scripts/fooext.tcl I mean: libh/lib/foo || libh/*/scripts/foo.tcl (scripts might not be "release-related". I see the release directory as tools fitting for the installer) Anyways, "extensions" don't necessarly need to be "part of" libh, they can simply have libh as a dependency, as long as we don't end up with a circular dependency. A. [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Pour information voir http://www.gnupg.org iEYEARECAAYFAj1TDK0ACgkQttcWHAnWiGe6xACeIlTNPimTOMvzV6PjQcF3DXnG Jh0AnAmKwoLd9jT40QFSel/0ahkbjsVr =UCZu -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020809002829.GA20585>