M. Edward (Ed) Borasky wrote: >> I don't see what is so dangerous about a server flag. After all I don't >> set doc globally, but it is a useful global flag, with clear intent, as >> would be server. >> >> If usr sets server on a box in make.conf, against advice, they still have >> to actually emerge the pkgs they want, after all. So it's not like it's >> going to lead to a mass of bloat (unlike the current setup.) >> > Actually, on my systems, about the only USE flags I *don't* set globally > in make.conf are "doc", "examples" and "source". There are very few > conflicts from this, and just about everything in my package.use file is > either making the documentation and examples or suppressing an option > for a package where it doesn't work. It turns out to be easier for me to > manage things that way than to have a humongous package.use and a few > options in make.conf.
With respect, I don't see how this affects anything to do with the flag? Eg for my personal use, I need KRB5, LDAP, SMB and mySQL. The only server I want is mySQL for local web-development with apache2, so I'd set server for dev-db/mySQL in package.use and leave it at that. I can understand that USE-conditional deps might be required, eg if a user (grr like you ppl don't know what usr means ;) wants a web-app it might require a db server. Firstly, I thought those were coming, and secondly in that case the user would I would think know that server software was needed, as s/he would be setting up a server app. A simple ewarn would suffice imo, since the db server might well be on another host. -- gentoo-dev@gentoo.org mailing list
