Everytime world update wants to update bacula, I get a full bacula installation instead of client only, because I forgot to set BUILD_CLIENT_ONLY beforehand. If this was a USE flag, people could set it once and forget about it. Reproducible: Always Steps to Reproduce:
A server use flag would need general acceptance. It was proposed once, got some opposition and shot down. You can read here http://www.mail-archive.com/gentoo-dev@gentoo.org/msg00401.html about it.
This package does have this client/server split, but not in a Gentoo typical way. I just asked to make it Gentoo compliant. If this is not wanted, then it should be removed alltogether.
The Gentoo compliant way is to install client and server part, if a package includes both. It doesn't matter so much, that you only have to set one variable for this package, but a consistent way Gentoo handles this for all packages is important; "server" is just too general to keep it local. I for one would favor client/server distinction, but it would be quite a lot of continued maintenance work for a whole lot of packages. We don't have enough ressources to achieve this, imho. If you want to see this changed, then post in the gentoo-dev ml. Chuck: Don't know if you'd think about splitting bacula in bacula-client and bacula-server.
Hmm, but isn't it the purpose of USE flags to allow the user to configure a package like he would do when running ./configure manually? And this is just what I'm asking for. bacula comes with a configure option "--enable-client-only". So there is no need to split the package into client and server. And controlling this configure option with an env var instead of a USE flag is not the Gentoo way, is it?
This is not a matter of a general server/client USE variable. What we're talking about here is a USE variable to make bacula build clientonly every time. USE="baculaclientonly" or something. Either that or split the package as suggested in bug #68317 (which would be a better solution anyway for installations that involve more than one machine).
