| 1 |
Josh Saddler wrote: |
| 2 |
> Mart Raudsepp wrote: |
| 3 |
>> I wanted to work at some point on splitting out gnome and kde profiles |
| 4 |
>> to separate ones. Perhaps desktop profile could be a generic universal |
| 5 |
>> one with USE flags enabled that rox/lxde/fluxbox and so on would like as |
| 6 |
>> well, and then gnome adds its stuff, and kde adds its own stuff. |
| 7 |
>> Or desktop could be one that enabled both GNOME and KDE stuff as now, by |
| 8 |
>> multi-inheriting both gnome and kde profiles. |
| 9 |
>> Or perhaps both a lowest common denominator desktop-base profile and a |
| 10 |
>> big desktop one enabling everything... |
| 11 |
> |
| 12 |
> What could be nice is if users could select multiple profiles. They |
| 13 |
> first choose the "desktop" profile, which has lots of basic stuff that's |
| 14 |
> DE/WM-agnostic. They could then select another profile that adds e.g. |
| 15 |
> Gnome stuff, like you suggested. |
| 16 |
|
| 17 |
It would be pretty trivial to use a PORTAGE_PROFILES variable in |
| 18 |
make.conf, to replace /etc/make.profile. You could do something like |
| 19 |
this: |
| 20 |
|
| 21 |
PORTAGE_PROFILES="/usr/portage/profiles/desktop |
| 22 |
/usr/portage/profiles/gnome" |
| 23 |
|
| 24 |
You could use this approach to pull in profiles from overlays too if |
| 25 |
desired. |
| 26 |
|
| 27 |
> I suppose the potential problem here (besides coding support for more |
| 28 |
> than one profile) is making sure that the selected profile's USE flags |
| 29 |
> (etc.) don't conflict with other selected profiles. Profile authors |
| 30 |
> would have to be pretty aware of what other profiles contain, and/or the |
| 31 |
> package manager would have to have some heavy duty resolver. |
| 32 |
|
| 33 |
I doubt that it will be much of an issue, but the dependency |
| 34 |
resolver will surely give you at least some kind of error if |
| 35 |
something goes wrong. |
| 36 |
|
| 37 |
> One could just avoid the whole multiple-profiles-selected thing by |
| 38 |
> cloning bits of one profile (like a minimal agnostic "desktop"), then |
| 39 |
> adding your own USE flags, and calling it the "Gnome" profile, but this |
| 40 |
> introduces lots of code duplication. |
| 41 |
|
| 42 |
Right now, users can combine multiple profiles by creating |
| 43 |
/etc/make.profile as a directory and adding as many profile paths as |
| 44 |
desired to the parent file (equivalent to the proposed |
| 45 |
PORTAGE_PROFILES approach, but using a file instead of a variable). |
| 46 |
-- |
| 47 |
Thanks, |
| 48 |
Zac |
Archives