Lines Matching refs:sets

22   of binary `sets', which the user can choose among at install time.
27   The current granularity of sets is very large, being divided into:
61   allowing users to choose among either `package sets' at the same
62   granularity as our current install sets, or individual `packages'
65   and sets at a later time, and would allow tracking of dependencies
66   between the various sets and packages distributed as part of NetBSD.
69   discussed, followed by the format of package sets, which will serve
70   as a replacement for the current install sets.  The creation of
112   EGCS utilities' packages.  Packages sets, described below, would add
114   like todays install sets, while maintaining the ability to remove
158   A look through the contents of the current install sets suggests
171   to install at once.  The introduction of `package sets', analogous
172   in granularity, but not mechanism, to the current binary install sets
178   These package sets will maintain the same layout as the current
179   install sets, so that a user who chooses the same sets as he would
181   however, these sets will be made up of binary packages, and installing
207   /usr/src/etc creates binary install sets from an installed system,
208   based on the set lists in /usr/src/distrib/sets/lists.  In the new
211   system packages and package sets.
213   The directory /usr/src/distrib/pkg/sets will contain a directory
216   /usr/src/distrib/pkg/sets will recurse into these set directories
235   sets, it will be possible to modify the various installation tools
236   to use these sets to install the system.  It is expected that
238   package sets at install time, but allow an `advanced mode' in which
251   My current plan for implementing system packages and package sets
287 	contents files and to create sets from each directory
288 	of packages in /usr/src/distrib/pkg/sets.