| 1 |
On Mon, 2005-08-29 at 11:59 -0400, Chris Gianelloni wrote: |
| 2 |
> As I understood it, they were implemented to reduce the amount of work |
| 3 |
> necessary in maintaining them. As it was back then, it required changes |
| 4 |
> to an extremely large number of profiles every time a change was made to |
| 5 |
> the default USE flags. |
| 6 |
Just a crazy idea - why not create a package containing some profiles? |
| 7 |
You can use the default profile, and if you want a different profile, |
| 8 |
"emerge portage-profiles" or whatever it is called and use that. I guess |
| 9 |
I've missed something obvious here? |
| 10 |
> I honestly don't think it would be a good idea |
| 11 |
> to forget the lessons of the past and start bloating the profiles with |
| 12 |
> tons of "desktop" and "server" profiles, among anything else people |
| 13 |
> would want. After all, as soon as we did a "desktop" profile, then we |
| 14 |
> would have requests for "gnome" and "kde" sub-profiles. |
| 15 |
which are not much work if kde = desktop -gtk -gnome +kde |
| 16 |
|
| 17 |
> As I stated earlier, it's easier to not provide *any* than to try to |
| 18 |
> provide all of the ones that will inevitably be requested as soon as we |
| 19 |
> start adding them. |
| 20 |
Or provide them in an extra ebuild that throws lots of warnings so that any users that don't read the warnings can be RESOLVED WONTFIXed? |
| 21 |
|
| 22 |
-- |
| 23 |
Stand still, and let the rest of the universe move |
Archives