1 |
On Sun, Feb 18, 2001 at 05:43:22PM -0500, Jerry A! wrote: |
2 |
> I'm thinking that this may be a good time to audit the portage tree and |
3 |
> clean up any cruft. |
4 |
> |
5 |
> Specifically: |
6 |
> |
7 |
> 1. Clean out directories with multiple, older versions of ebuilds. |
8 |
> 2. Consolidate portages which are replicated in multiple directories. |
9 |
> 3. Consolidate current-packages and current-packages.new into one file. |
10 |
> |
11 |
> Why now? Well, since it looks like most of Gentoo is falling into place |
12 |
> and is growning everyday, now seems like a good time (in my opinion). |
13 |
> Also, it appears as though with the new portage expansions (xpak) being |
14 |
> the building blocks for 1.0_rc5, that this going into this with a |
15 |
> spotless tree may make the work a lot easier. |
16 |
> |
17 |
> Anyway, I'd like to know what you all think. If it does appear like a |
18 |
> good idea, then maybe we should get all the committers together, divide |
19 |
> up the tree and go to town... |
20 |
|
21 |
I think that's a good idea. We may want to start discussing how to add a new |
22 |
feature to portage called "system profiles". This new feature will allow us to |
23 |
define a certain "type" of Gentoo Linux system, and then list all the packages |
24 |
that are part of this system. Users will be able to select from these various |
25 |
types at system install time. For example, a user can decide to install a |
26 |
"minimal server" set of packages, or a "the drobbins ultimate desktop system" |
27 |
set. I plan to record user profile information in /usr/portage/profiles, and |
28 |
it will allow us to replace the current-packages file with a |
29 |
/usr/portage/profiles/default file. |
30 |
|
31 |
Now, some questions. |
32 |
|
33 |
I still haven't decided how this system will work with the USE variable. Right |
34 |
now, optional functionality can be enabled or disabled with USE in make.conf, |
35 |
so that ebuilds know whether to compile-in optional GNOME support into |
36 |
particular packages, for example. Will system profiles include their own |
37 |
custom USE settings? It would seem like they'd have to. They may also have |
38 |
other special customization files -- any you can think of? |
39 |
|
40 |
The USE variable also creates some complications for our .tbz2 binaries that |
41 |
appear on the CD. What should the default USE settings be? I'm thinking that |
42 |
our binaries could cater to a fully-configured system. If users want to set |
43 |
up a minimal system, then can install the sys.tbz2 file, set USE appropriately, |
44 |
and then compile everything else from sources. |
45 |
|
46 |
Ideas, questions, comments? |
47 |
|
48 |
-- |
49 |
Daniel Robbins <drobbins@g.o> |
50 |
President/CEO http://www.gentoo.org |
51 |
Gentoo Technologies, Inc. |