Tom Wijsman wrote: > > portage should say, with as similar wording as possible: > > > > "If you want to emerge libXt with those USE flags then you'll also > > have to set those same USE flags for libYt and libZt because libXt > > DEPENDs on them." > > > > Bonus points: > > > > "Would you like me to set those USE flags for libYt and libZt for > > you? [Y/n]" > > Which part of this warns the user that the user is about to run into > something broken / experimental? We need to add that too, because it is > not clear from the output that you suggest. And if we add that as well, > it gets to be quite long;
It gets one word longer: "If you want to emerge libXt with those experimental USE flags then you'll also have to set those same USE flags for libYt and libZt because libXt DEPENDs on them." > how would we condense that? If something is a bit complicated then a bit more verbosity can be really good. //Peter
pgpCEQB4bI4gC.pgp
Description: PGP signature
