| 1 |
Okay, I think I got it. I saw that rrdtool was installed, so assumed everything was okay. But, what I didn't realize is that - back then - I guess I tried to install montorix and didn't notice, in the jungle of messages, that the emerge was not successful. |
| 2 |
|
| 3 |
Apparently, rddtool got installed with harmless, default values, which, however, are not sufficient for monitorix. So, now I can accept the changes, and re-emerge rddtool - or probably, emerging monitorix will arrange for that. |
| 4 |
|
| 5 |
Then, if someday, I get a nasty message that there's a keyword conflict, I'll have to sacrifice either the new package or monitorix ... |
| 6 |
|
| 7 |
In the meantime, I'll install this package and that, and some of them may be dependent on rrdtool. In that case, unless they explicitly disallow that unmasked version, they'll use the same, possibly experimental, version. When the day comes that I have to back the unmasked version of rrdtool out, then all other dependent packages will get the standard, default version again. |
| 8 |
|
| 9 |
I'm catching on, bit by bit ;-) |
| 10 |
|
| 11 |
|
| 12 |
|
| 13 |
> Gesendet: Dienstag, 04. Juni 2019 um 00:50 Uhr |
| 14 |
> Von: "Mick" <michaelkintzios@×××××.com> |
| 15 |
> An: gentoo-user@l.g.o |
| 16 |
> Betreff: Re: Aw: Re: [gentoo-user] Updating portage, continued |
| 17 |
> |
| 18 |
> On Monday, 3 June 2019 23:09:40 BST n952162@×××.de wrote: |
| 19 |
> > I'm sorry, I'm not getting this yet. What if I just don't update these |
| 20 |
> > configuration files? |
| 21 |
> > |
| 22 |
> > dispatch-conf tells me, for /etc/portage/package.accept_keywords: |
| 23 |
> > |
| 24 |
> > --- /etc/portage/package.use/zz-autounmask 2018-03-12 |
| 25 |
> > 21:56:49.172491972 +0100 +++ |
| 26 |
> > /etc/portage/package.use/._cfg0015_zz-autounmask 2018-07-28 |
| 27 |
> > 11:08:23.725995803 +0200 @@ -1,2 +1,5 @@ |
| 28 |
> > |
| 29 |
> > >=dev-lang/python-2.7.14-r1:2.7 sqlite |
| 30 |
> > >=sys-libs/zlib-1.2.11-r1 minizip |
| 31 |
> > |
| 32 |
> > +# required by www-misc/monitorix-3.9.0::gentoo |
| 33 |
> > +# required by monitorix (argument) |
| 34 |
> > +>=net-analyzer/rrdtool-1.6.0-r1 perl graph |
| 35 |
> |
| 36 |
> If you accept the above portage will emerge net-analyzer/rrdtool-1.6.0-r1 with |
| 37 |
> USE flags 'perl' and 'graph' enabled. This change seems to be required by |
| 38 |
> www-misc/monitorix for some functionality of rrdtool (e.g. graphing) it needs. |
| 39 |
> |
| 40 |
> |
| 41 |
> > I can zap it or merge it or skip it. It looks like the emerge was |
| 42 |
> > successful, so, why should I do anything? |
| 43 |
> > |
| 44 |
> > $ rrdtool |
| 45 |
> > RRDtool 1.6.01.6.0 Copyright by Tobias Oetiker <tobi@×××××××.ch> |
| 46 |
> |
| 47 |
> Successful against what criteria? If monitorix needs/wants it to be compiled |
| 48 |
> so in order to perform graphing, it may not work until you've enabled these |
| 49 |
> USE flags and re-emerged (more successfully this time) rrdtool. |
| 50 |
> |
| 51 |
> |
| 52 |
> > I would have thought that emerge would pend until I'd agreed to the |
| 53 |
> > override. But, it apparently went ahead and installed. So what's required |
| 54 |
> > still? What will be different once I make the merge to zz-autounmask? |
| 55 |
> |
| 56 |
> If the changes in USE flags were hardcoded in the ebuild, because without them |
| 57 |
> an insurmountable conflict would arise, I expect portage would refuse to |
| 58 |
> emerge and complain of a hard block [B]. |
| 59 |
> |
| 60 |
> -- |
| 61 |
> Regards, |
| 62 |
> Mick |
Archives