On Mon, 2005-08-29 at 11:59 -0400, Chris Gianelloni wrote: > As I understood it, they were implemented to reduce the amount of work > necessary in maintaining them. As it was back then, it required changes > to an extremely large number of profiles every time a change was made to > the default USE flags. Just a crazy idea - why not create a package containing some profiles? You can use the default profile, and if you want a different profile, "emerge portage-profiles" or whatever it is called and use that. I guess I've missed something obvious here? > I honestly don't think it would be a good idea > to forget the lessons of the past and start bloating the profiles with > tons of "desktop" and "server" profiles, among anything else people > would want. After all, as soon as we did a "desktop" profile, then we > would have requests for "gnome" and "kde" sub-profiles. which are not much work if kde = desktop -gtk -gnome +kde
> As I stated earlier, it's easier to not provide *any* than to try to > provide all of the ones that will inevitably be requested as soon as we > start adding them. 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? -- Stand still, and let the rest of the universe move
signature.asc
Description: This is a digitally signed message part
