1 |
Quoting Michał Górny (2017-08-15 08:43:07) |
2 |
> On wto, 2017-08-15 at 06:55 +0200, tomjbe@g.o wrote: |
3 |
> > Quoting Rich Freeman (2017-08-15 00:29:19) |
4 |
> > > On Mon, Aug 14, 2017 at 5:55 PM, Michał Górny <mgorny@g.o> wrote: |
5 |
> > > > On pon, 2017-08-14 at 21:58 +0200, Thomas Beierlein wrote: |
6 |
> > > > > |
7 |
> > > > > * 'bacula-clientonly' becomes 'clientonly' |
8 |
> > > > |
9 |
> > > > This is still negative logic in disguise. clientonly = noserver. |
10 |
> > |
11 |
> > True. See below for discussion. |
12 |
> > > > |
13 |
> > > > > * 'bacula-nodir' will be replaced by 'director' but with inverted logic |
14 |
> > > > > * 'bacula-nosd' will be replaced by 'storage-daemon' (also inverted). |
15 |
> > > > > |
16 |
> > > > > 'director' and 'storage-daemon' will be active by default resulting in an |
17 |
> > > > > installation with backup director and storage daemon enabled. |
18 |
> > > > > |
19 |
> > > |
20 |
> > > ++ |
21 |
> > > |
22 |
> > > I guess to make it a bit more explicit, would it make sense to have 3 flags: |
23 |
> > > |
24 |
> > > client - install the client (or consider calling it file-daemon instead) |
25 |
> > > director - install the director |
26 |
> > > storage-daemon - install the storage daemon |
27 |
> > > |
28 |
> > |
29 |
> > That would be best, but it is not supported by their (autoconf based) build |
30 |
> > system (and would require a complete rewrite of it). The actual USE flags |
31 |
> > mostly mirrors the switches from the configure script. You can not set them as |
32 |
> > you like, they are not orthogonal E.g. the file deamon (client) will be |
33 |
> > installed unconditionally. |
34 |
> > |
35 |
> > The configure script itself is very brittle atm and needs an urgent overhaul. |
36 |
> > Discussion with upstream goes a long way, but they do not want to change it |
37 |
> > because of the need to retest it on very different systems. No good situation. |
38 |
> > |
39 |
> > A possible idea may be to drop the 'no/client' flag completely. If neither |
40 |
> > 'director' nor 'storage-daemon' is active all that is left would be the |
41 |
> > file daemon. |
42 |
> > What do you think? |
43 |
> |
44 |
> WFM. If the flag doesn't do anything except for disabling the two other |
45 |
> flags, then there's no place for such a flag. |
46 |
> |
47 |
And here comes the problem. USE="bacula-nodir bacula-nosd" does not produce |
48 |
the same set of files as USE="bacula-clientonly". But I will recheck if the |
49 |
difference is of relevance for normal gentoo user. |
50 |
|
51 |
> > |
52 |
> > The downside of that idea is that we diverge from baculas documentation which |
53 |
> > explicitly state that there is a 'clientonly' install. |
54 |
> > |
55 |
> |
56 |
> Upstream install documentation is not relevant to Gentoo. The flag |
57 |
> descriptions in metadata.xml are. |
58 |
> |
59 |
Right. But if we drop a "clientonly" than there is no hint in metadata.xml how |
60 |
to get only the file daemon alone. Some einfo output or similar come to mind. |
61 |
|
62 |
Regards, |
63 |
|
64 |
Thomas |