Fabio Erculiani posted on Sun, 02 Sep 2012 16:45:12 +0200 as excerpted: > - If SDEPEND contains USE flags, these are written in stone and cannot > be changed without a rebuild. This is generally fine for source > packages, a bit less for binpkgs, but not really a big deal IMO.
This being the case, don't we effectively already have the feature in the form of default-use? Isn't a USE flag defaulted-on in effect ALREADY a "suggestion"? That seems to me to be how it's used in practice. For a new "suggested" mechanism to be actually worth the implementation cost, I'd /suggest/ that it must allow flipping state without a rebuild. Otherwise we effectively already have it in the form of default-use, so what's the point? Now it's certainly possible to argue that once one sets a global USE flag, the visibility of default-use "suggests" isn't particularly high, and that ideally --ask and --pretend with --verbose (and presumably whatever corresponds in the other PMs) should somehow emphasize "suggest" state a bit more than simply "it's there, make your own choice" state, which is arguably what normal use flags are, but that's a PM UI issue, not a lack of ability to mark "suggests" in the ebuild. Unless I'm missing something, the information's already expressible in the ebuild with existing default-use; it just arguable needs a bit more emphasis in the UI /as/ suggests, because that's what default-use in effect already IS. -- 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
