Lines Matching +full:- +full:- +full:no +full:- +full:install +full:- +full:suggests
5 --------
17 ------------------------------------------------------------------------
22 of binary `sets', which the user can choose among at install time.
24 to '/'. No facility exists to choose convenient subsets of the files
29 base -- general system binaries
30 comp -- compilers and related tools
31 etc -- system configuration files
32 games -- games and other amusements
33 man -- system manual pages
34 misc -- items not falling into other categories
35 secr -- items not exportable under US law
36 text -- text processing tools
37 xbase -- general X11R7 binaries
38 xcomp -- X11R7 development items
39 xfont -- X11R7 fonts
40 xserver -- X11R7 servers for various video hardware
42 Users who wish to install part of a set need to either install
44 or abandon the normal install process, and figure out which files
58 these and other problems with the current install set system by
59 moving to the use of fine-grained `system packages', based on the
60 currently existing package system for third-party software, and
62 granularity as our current install sets, or individual `packages'
70 as a replacement for the current install sets. The creation of
82 ------------------------------------------------------------------------
87 At install time, the user will choose which system packages to install,
88 subject to dependencies between packages. After system install,
89 users will be able to install additional packages or remove installed
92 functionality is already available for third-party software via the
99 used by the current third-party package system. This will allow the
101 currently used for working with third-party packages. This will also
113 the ability to choose entire broad categories of software to install,
114 like todays install sets, while maintaining the ability to remove
137 allow a client to install only those parts of the system which reside
141 Alistair Crooks in a post to the netbsd-current mailing list on
143 committed cause third-party software packages installed in /usr/pkg
155 The second step, that of insuring that a client can choose to install
158 A look through the contents of the current install sets suggests
159 that relatively few packages will in fact need to install in more
162 users would easily be able to install only the parts which are local
165 ------------------------------------------------------------------------
169 In moving to fine-grained system packages, it is important that
171 to install at once. The introduction of `package sets', analogous
172 in granularity, but not mechanism, to the current binary install sets
174 users to choose among individual packages at install time, and
179 install sets, so that a user who chooses the same sets as he would
193 contents file itself will be automatically generated from the one-line
198 current third-party package system. This will allow users to remove
202 ------------------------------------------------------------------------
206 Under the current distribution-building system, the Makefile in
207 /usr/src/etc creates binary install sets from an installed system,
224 third-party software packages in /usr/pkgsrc, except that they will
230 ------------------------------------------------------------------------
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
242 be present on install media to be used with system packages.
243 Modifications to sysinst and other install tools are beyond the
247 ------------------------------------------------------------------------
269 be to create either an actual or mocked-up system package
292 install process to use them. It is important to note that none
297 ------------------------------------------------------------------------