Subject: Re: Firewall packages
To: Bernd Salbrechter <firstname.lastname@example.org>
From: Manuel Bouyer <email@example.com>
Date: 09/15/2000 21:32:02
On Thu, Sep 14, 2000 at 09:32:06PM +0200, Bernd Salbrechter wrote:
> Hey wouldn't it make more sense to classify the parts of a package and
> add options to pkg_add to install only those parts the user wants.
> Is there some need to strip down the distribution sets also?
> I could identify the following part in a package:
> 1. RUN-TIME: what's need to work with the pkg.
> 2. DOCUMENTATION: the online documentation, which is nice to have.
> 3. DEVELOPMENT: what's need to develop other packages using this one.
> This will be a superset of "RUN-TIME", but not including
> DOCUMENTATION (you can have this somewhere else).
> 4. CONFIGURATION: default configuration files.
> 5. EXAMPLES: Files that can be used to give the user some results he
> can look on (i.e. tiger.ps in ghostscript).
> Should this be split into RUN-TIME, DEVELOPMENT and CONFIGURATION?
> 6. MESSAGE-CATALOGS: I'm sure not everyone need all languages, but more
> than one can be quite common. Dictionaries for several languages
> are better handled as separate packages. This will need a way to
> install all message catalogs for a set of given languages for all
> installed packages.
Please also add:
7. SHARE: all files under the share directory (supposed to be MI and shared
accros multiple architectures). This can he handy for machines which mount
share from another one.
Manuel Bouyer <firstname.lastname@example.org>