Quoting Rich Freeman (2017-08-15 00:29:19) > On Mon, Aug 14, 2017 at 5:55 PM, Michał Górny <mgo...@gentoo.org> wrote: > > On pon, 2017-08-14 at 21:58 +0200, Thomas Beierlein wrote: > >> > >> * 'bacula-clientonly' becomes 'clientonly' > > > > This is still negative logic in disguise. clientonly = noserver.
True. See below for discussion. > > > >> * 'bacula-nodir' will be replaced by 'director' but with inverted logic > >> * 'bacula-nosd' will be replaced by 'storage-daemon' (also inverted). > >> > >> 'director' and 'storage-daemon' will be active by default resulting in an > >> installation with backup director and storage daemon enabled. > >> > > ++ > > I guess to make it a bit more explicit, would it make sense to have 3 flags: > > client - install the client (or consider calling it file-daemon instead) > director - install the director > storage-daemon - install the storage daemon > That would be best, but it is not supported by their (autoconf based) build system (and would require a complete rewrite of it). The actual USE flags mostly mirrors the switches from the configure script. You can not set them as you like, they are not orthogonal E.g. the file deamon (client) will be installed unconditionally. The configure script itself is very brittle atm and needs an urgent overhaul. Discussion with upstream goes a long way, but they do not want to change it because of the need to retest it on very different systems. No good situation. A possible idea may be to drop the 'no/client' flag completely. If neither 'director' nor 'storage-daemon' is active all that is left would be the file daemon. What do you think? The downside of that idea is that we diverge from baculas documentation which explicitly state that there is a 'clientonly' install. Thomas.
