ufed loses currently used flags. ugly. this should be fixed? Reproducible: Always Steps to Reproduce: 1.emerge ufed 2.ufed 3.save -> old USE flags from /etc/make.conf is lost
Since ufed doesn't work with stacked profiles and empty make.defaults, I for one think a warning is in order and ufed should be hard masked.
Created attachment 47273 [details, diff] UFED support for stacked profiles' make.defaults This patch provides ufed with preliminary support for stacked profiles, in that it follows the profiles' parent links, during its parsing of the make.default files. This includes ignoring any empty make.defaults files. I'd think that more work on handling /etc/portage/* and package use flags is still required. Like ufed this patch is distributed under the terms of the GPLv2
ufed still doesnt work correctly for me (the -r3 release) ... need to touch /etc/make.profile/make.defaults before running it, else it would spit out a bunch of errors (indicating that the above file is missing), and then start up showing bogus flags :( this is on ppc, using the 2005.0 profile
If you lost your USE flags from this, one way be to run: emerge -pvN world|grep \* -v shows the use flags that are used by packages, and there will be an * by ones that have changed since they were compiled. -N will only emerge packages that have changed So this should give you a good idea of what flags you lost. This wouldn't, however, help with use flags that the system hasn't actually made use of.
Created attachment 55230 [details, diff] revised UFED support for stacked profiles' make.defaults This is a revised version of the stacked profiles patch. It simply adds a test if ( -e "$path/$file" ) inside sub inherit_parent. This seems to correct the issue reported in comment #3.
Should be working with ufed 0.36. Please reopen if that still has problems.
