| 1 |
On Tue, 01 Jul 2003 15:12:20 +0100 |
| 2 |
Dhruba Bandopadhyay <dhruba@××××××××××××.uk> wrote: |
| 3 |
|
| 4 |
> Seemant Kulleen wrote: |
| 5 |
> > The idea stems from the fact that etc-updating a make.conf file can be a bit |
| 6 |
> > of a stressful event. |
| 7 |
> > And as portage's set of features grows, so too will the size of the |
| 8 |
> > make.conf file. |
| 9 |
|
| 10 |
> I suggest /etc/portage/. There is already a dir structure for |
| 11 |
> /etc/portage/package.unmask. As a result, it would make sense for all |
| 12 |
> portage/gentoo related files to be placed in there. This would include |
| 13 |
> make.conf, rc.conf, help files and any others. |
| 14 |
> |
| 15 |
> To summarise, directory structure: yes, dynamic: yes, from zillions of |
| 16 |
> smaller files: no (that's backward progress). |
| 17 |
> |
| 18 |
> A few of my thoughts. |
| 19 |
> |
| 20 |
I don't actually see how rc.conf comes into game? I don't know about you but my |
| 21 |
rc.conf has 7 vars set, like font for the console, display manager etc. Nothing |
| 22 |
to do with portage at all. |
| 23 |
|
| 24 |
However I agree with you that generating it from millions of small file is not |
| 25 |
a sollution of a problem. What would be much better is to have a utility for |
| 26 |
that. It has been discussed here about two weeks ago. The idea was to have a |
| 27 |
tool to set all gentoo-specific vars, including ones in make.conf IMHO that's |
| 28 |
quite a good solution. |
| 29 |
|
| 30 |
|
| 31 |
-- |
| 32 |
Sergey Kuleshov <svyatogor@g.o> |
| 33 |
Let the Force be with us! |
| 34 |
|
| 35 |
-- |
| 36 |
gentoo-dev@g.o mailing list |
Archives