1 |
On Mon, 2002-11-18 at 17:41, David Olsen wrote: |
2 |
> On 2002-11-18-09:53:03, Felipe Ghellar <fghellar2@×××××××××.br> wrote: |
3 |
> > What about including it in the variable FEATURES in make.conf? |
4 |
> > |
5 |
> > FEATURES="sandbox ccache prelink" |
6 |
> |
7 |
> Prelinking may be more suited as a USE variable, just an opinion though. |
8 |
> |
9 |
|
10 |
I am siding on the side of "FEATURES" as prelinking globally effects |
11 |
binaries and libraries, you cannot always say that certain libraries are |
12 |
not to be prelinked, as USE flags would imply. |
13 |
|
14 |
Also you would have a messy problem on uninstall having to read the USE |
15 |
flags. Although you could choose to always uninstall in the prelink safe |
16 |
way. |
17 |
|
18 |
Plus it fits better into the portage overview to have USE flags effect |
19 |
the behaviour of the ebuild code and FEATURES flags effect the portage |
20 |
(python) code. |
21 |
|
22 |
My two pence , |
23 |
|
24 |
-- |
25 |
Stefan Jones <cretin@g.o> |
26 |
Gentoo Linux |
27 |
|
28 |
|
29 |
-- |
30 |
gentoo-dev@g.o mailing list |