Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
List Archive: gentoo-portage-dev
I've finished my superkaramba theme, but I'm noticing one bug that I
think has something to do the way emerge or portage modules are
written that I don't understand.
Basically, I've trimmed everything in emerge down that doesn't
directly deal with system or a world update. I import my trimmed
emerge module and call the a main function I created that contains
what was done automatically in the regular emerge.
Everything works but after loading the superkaramba theme, if I change
a useflag in package.use, doing a emerge '-puvDN sysmte' doesn't
recognize the change. I'm wondering what could be causing this?
In case the above doesn't make sense, here's what i mean.
1. load superkaramba theme
2. do a 'emerge -puvDN system', everything correct at this point
3. change use flag in package.use
4. do a 'emerge -puvDN system' again, result still same from point 2,
emerge not picking up the changed use flag
Is there something in emerge that needs to be reset other than whats
initialized at the beginning for it to recognize changes in
package.use after loading module?
Here's a copy of the trimmed down emerge, but that shouldn't be need
as it remains the same.
http://www.tomek.ca/websvn/filedetails.php?repname=portage-monitor&path=%2Fportage_engine.py&rev=0&sc=0
--
Tom
--
gentoo-portage-dev@g.o mailing list
|
|