Georgi Georgiev wrote:
maillog: 14/01/2005-11:23:18(+0000): Ciaran McCreesh types
Now, you could argue that x86-sse would be a better name for the flag,
but since we can't really do USE renames it's kinda moot.
What's wrong with USE renames? Portage already fixes
/etc/portage/package.* when a package moves, what's wrong with fixing
user's make.conf as well? Fixing the ebuilds might take a bit of time,
but a sed and then just looking over the diff to make sure something has
not been automated should do the trick?
Well from a user point of view, those are my files, not portages. You
don't mess with /etc/portage/profile or /etc/make.conf. I remember
seeing a bug filed where someone had masked xfree and portage rewrote
his use file to have xorg there instead. He wasn't too happy to have
that happen ( and wondered wtf it was since he didn't recall a message
telling him that portage had fixed his profile ). I wasn't particularly
glad to see that happen either. You generally don't want portage to be
touching stuff like that ( CONFIG_PROTECT it by default perhaps. )
otherwise I could potentially file bugs in portage for doing dumb crap
to my profile settings. Why does portage have to 'automagically' fix
things like that?
--
Alec Warner
Spartasoft Secretary ( spartasoft.msu.edu )
Junior Computer Science
Michigan State University
[EMAIL PROTECTED]
--
[email protected] mailing list
