1 |
Hi, first of all, i'd like to say how much i appreciate the goals of |
2 |
portage-ng's rewrite :) |
3 |
|
4 |
That having said, i would like to be able to specify a specific build |
5 |
environment for some packages, manually modifying the environment for |
6 |
emerge is just not sufficient. |
7 |
|
8 |
May i propose a /etc/portage/portage.d directory, where i could create, |
9 |
say a /etc/portage/portage.d/net-fs/samba/make.conf file which would |
10 |
modify the normal build environment. |
11 |
|
12 |
for example, my /etc/portage/portage.d/net-fs/samba/make.conf file |
13 |
would contain : |
14 |
|
15 |
USE="-ldap" |
16 |
|
17 |
this way i know that if samba gets upgraded, i won't have to recompile |
18 |
it myself with USE="-samba" emerge ... samba. |
19 |
|
20 |
and maybe even a /etc/portage/portage.d/net-misc/jigdo/make.conf file |
21 |
with : |
22 |
|
23 |
ACCEPT_KEYWORDS="~x86" |
24 |
|
25 |
so that if jigdo gets updated in ~x86 and i run x86 keywords (i do), |
26 |
jigdo will get updated (portage would know that i build jigdo with |
27 |
~x86). |
28 |
|
29 |
|
30 |
Yeah, that's it, with maybe some mechanism to provide slot-specific |
31 |
informations, maybe ... |
32 |
|
33 |
|
34 |
|
35 |
-- |
36 |
gentoo-portage-dev@g.o mailing list |