On Mon, Aug 29, 2005 at 12:56:35PM -0400, Chris Gianelloni wrote:
> On Sat, 2005-08-27 at 05:01 -0500, Brian Harring wrote:
> Basically, you've taken then 2005.1 profile and made it useless, since
> the stages weren't built against it anyway.
Via that logic (don't change it lest it negates a release), we would 
never be able to do changes, or would be forced to do changes strictly 
whenever y'all are doing a new release.

Profiles aren't bound to the releases, despite how people may view it 
and/or the current profile maitnainer's usage of 'em.

>  My point is pretty simple,
> why should we spend a bunch of time maintaining something that is
> designed from the start to be customized, and most likely won't even be
> used anyway?
That's the issue; the profiles in their current form are customizable 
only in the ability to negate a collection of flags.
Negating the whole beast is another story due to the desktop cruft 
being shoved into the arch subprofiles.

> I would much rather stick with the "2005.1" profile
> meaning "what we used to build 2005.1" than having it mean "some
> variation of 2005.1 is below here and using this profile is minimal and
> likely won't do what you expect".
Again, releases may be bound by available profiles, but available profiles 
are not bound by available releases.

Aside from that, the comments about variations/minimal/not doing what 
you expect, what do you think USE="-* user's actual desired flags" 
accomplishes?

Profile customization occurs, /etc/portage/profiles exists for this 
reason; the 2005.1 profile (fex) is probably *rarely* ran exactly as 
y'all have it specified considering we do have user level use flags, 
tweaking the hell out of '05.1.

Aside from mild disagreement on views, as was stated in previous 
emails, multiple inheritance I tend to think is required to minimize 
the work for y'all; what I want you guys to do (or I'll do myself) is 
chunk the suckers up so people after a minimal base for running 
it themselves, or building up their own subprofile can do so.  Not 
after jamming maintenance nightmares on you, which without multiple 
inheritance, might be a bit.

~harring

Attachment: pgpnO9KjjXNG9.pgp
Description: PGP signature

Reply via email to