Ciaran McCreesh posted on Mon, 13 Apr 2015 17:49:13 +0100 as excerpted: > On Mon, 13 Apr 2015 06:36:44 +0000 (UTC) > Duncan <[email protected]> wrote: >> What about "initial-build" for the flag name, and making it part of the >> next EAPI, such that PMs know how to handle it without involving the >> user having to set it, and indeed, actually ignore the flag (as a >> masked flag) in normal operation if the user /does/ set it? > > You haven't thought your cunning plan all the way through. What if cmake > is installed but broken and needing a revdep-rebuild?
Two ways to deal with that. 1) Unmerge cmake, so it's an initial build again. (Depending on the conflict, an unmerge/clean-merge being the simplest resolution isn't uncommon. With all of @world in subsets here, portage unmerges, with a warning either that it's still in set X, or that it's a dep, so it never leaves @world and a standard emerge @world will bring it back.) 2) Masked USE flag, so users can override the same way they can other masked USE flags. Also, being a masked USE flag, it's displayed, just as masked, so a user can know it's there. Tho your point remains valid at some level as those are both "advanced" hoops that a user arguably shouldn't be /forced/ to jump thru, even if doing so might be the most convenient fix, at times. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
