1 |
On Tuesday, 4 June 2019 21:21:24 BST n952162@×××.de wrote: |
2 |
> Or, perhaps, that's where slots come in? |
3 |
> |
4 |
> If I try to install package A, which doesn't want whatever's in |
5 |
> |
6 |
> > > > +>=net-analyzer/rrdtool-1.6.0-r1 perl graph |
7 |
> |
8 |
> then, it'll use a new slot? |
9 |
|
10 |
Not really. rrdtool-1.x will be in the same slot, say SLOT="0" for whichever |
11 |
x value the developers release. You will not be able to install rrdtool-1.x |
12 |
and rrdtool-1.xx, without using a prefix or some similar trick. |
13 |
|
14 |
If the developers also released a different slot, e.g. rrdtool-2.x, then this |
15 |
would become SLOT="1" and so on, with its own different versions of build and |
16 |
run time dependencies. You could conceivably have both rrdtool-1.x and |
17 |
rrdtool-2.x installed on the same box, with different USE flags is you so |
18 |
wished or the devs or make.profile stipulated - as long as there was no major |
19 |
blockage in their respective versions of dependencies. |
20 |
|
21 |
Have a look here for a better explanation of SLOTS: |
22 |
|
23 |
https://devmanual.gentoo.org/general-concepts/slotting/ |
24 |
|
25 |
|
26 |
> I see that I have ebuilds for rrdtool-1.6.0 and rrdtool-1.7.0,1.7.1. and |
27 |
> 1.7.2. The one that runs when I enter rrdtool is 1.6.0. |
28 |
|
29 |
They all belong to the same slot: |
30 |
|
31 |
$ grep SLOT /usr/portage/net-analyzer/rrdtool/rrdtool-1.*.ebuild |
32 |
/usr/portage/net-analyzer/rrdtool/rrdtool-1.6.0-r1.ebuild:SLOT="0/8.0.0" |
33 |
/usr/portage/net-analyzer/rrdtool/rrdtool-1.7.0.ebuild:SLOT="0/8.0.0" |
34 |
/usr/portage/net-analyzer/rrdtool/rrdtool-1.7.1.ebuild:SLOT="0/8.0.0" |
35 |
/usr/portage/net-analyzer/rrdtool/rrdtool-1.7.2.ebuild:SLOT="0/8.0.0" |
36 |
|
37 |
|
38 |
> Was that caused by etc/portage/package.use/._cfg0015_zz-autounmask even |
39 |
> though I hadn't accepted it yet? I understand correctly, right, that |
40 |
> commands in ._cfg* files pend until accepted? |
41 |
|
42 |
Yes. Configuration directives in ._cfg* files remain there until accepted or |
43 |
until rejected (zapped) by the user. |
44 |
|
45 |
|
46 |
> Basically, this pending change is because monitorix doesn't want to work |
47 |
> with the newest version of rrdtool? |
48 |
|
49 |
I think it is a matter of USE flags monitorix requires of rrdtool. Looking in |
50 |
the latest stable monitorix ebuild we see: |
51 |
|
52 |
RDEPEND="dev-perl/Config-General |
53 |
dev-perl/DBI |
54 |
dev-perl/HTTP-Server-Simple |
55 |
dev-perl/IO-Socket-SSL |
56 |
dev-perl/libwww-perl |
57 |
dev-perl/MIME-Lite |
58 |
dev-perl/XML-Simple |
59 |
net-analyzer/rrdtool[graph,perl] <== This one |
60 |
dev-perl/CGI" |
61 |
|
62 |
These USE flag requirements for rrdtool are present in all versions of |
63 |
monitorix presently in the tree, see below, but things may have been different |
64 |
in previous monitorix versions not currently in the tree (I'm not familiar |
65 |
with monitorix and its historic dependencies): |
66 |
|
67 |
$ grep rrdtool /usr/portage/www-misc/monitorix/monitorix-*.ebuild |
68 |
/usr/portage/www-misc/monitorix/monitorix-3.10.0-r1.ebuild: net-analyzer/ |
69 |
rrdtool[graph,perl] |
70 |
/usr/portage/www-misc/monitorix/monitorix-3.10.1.ebuild: net-analyzer/ |
71 |
rrdtool[graph,perl] |
72 |
/usr/portage/www-misc/monitorix/monitorix-3.11.0.ebuild: net-analyzer/ |
73 |
rrdtool[graph,perl] |
74 |
/usr/portage/www-misc/monitorix/monitorix-3.9.0.ebuild: net-analyzer/ |
75 |
rrdtool[graph,perl] |
76 |
|
77 |
|
78 |
> > Gesendet: Dienstag, 04. Juni 2019 um 21:56 Uhr |
79 |
> > Von: n952162@×××.de |
80 |
> > An: gentoo-user@l.g.o |
81 |
> > Betreff: Aw: Re: Re: [gentoo-user] Updating portage, continued |
82 |
> > |
83 |
> > Okay, I think I got it. I saw that rrdtool was installed, so assumed |
84 |
> > everything was okay. But, what I didn't realize is that - back then - I |
85 |
> > guess I tried to install montorix and didn't notice, in the jungle of |
86 |
> > messages, that the emerge was not successful. |
87 |
> > |
88 |
> > Apparently, rddtool got installed with harmless, default values, which, |
89 |
> > however, are not sufficient for monitorix. So, now I can accept the |
90 |
> > changes, and re-emerge rddtool - or probably, emerging monitorix will |
91 |
> > arrange for that. |
92 |
> > |
93 |
> > Then, if someday, I get a nasty message that there's a keyword conflict, |
94 |
> > I'll have to sacrifice either the new package or monitorix ... |
95 |
> > |
96 |
> > In the meantime, I'll install this package and that, and some of them may |
97 |
> > be dependent on rrdtool. In that case, unless they explicitly disallow |
98 |
> > that unmasked version, they'll use the same, possibly experimental, |
99 |
> > version. When the day comes that I have to back the unmasked version of |
100 |
> > rrdtool out, then all other dependent packages will get the standard, |
101 |
> > default version again. |
102 |
> > |
103 |
> > I'm catching on, bit by bit ;-) |
104 |
> > |
105 |
> > > Gesendet: Dienstag, 04. Juni 2019 um 00:50 Uhr |
106 |
> > > Von: "Mick" <michaelkintzios@×××××.com> |
107 |
> > > An: gentoo-user@l.g.o |
108 |
> > > Betreff: Re: Aw: Re: [gentoo-user] Updating portage, continued |
109 |
> > > |
110 |
> > > On Monday, 3 June 2019 23:09:40 BST n952162@×××.de wrote: |
111 |
> > > > I'm sorry, I'm not getting this yet. What if I just don't update |
112 |
> > > > these |
113 |
> > > > configuration files? |
114 |
> > > > |
115 |
> > > > dispatch-conf tells me, for /etc/portage/package.accept_keywords: |
116 |
> > > > |
117 |
> > > > --- /etc/portage/package.use/zz-autounmask 2018-03-12 |
118 |
> > > > 21:56:49.172491972 +0100 +++ |
119 |
> > > > /etc/portage/package.use/._cfg0015_zz-autounmask 2018-07-28 |
120 |
> > > > 11:08:23.725995803 +0200 @@ -1,2 +1,5 @@ |
121 |
> > > > |
122 |
> > > > >=dev-lang/python-2.7.14-r1:2.7 sqlite |
123 |
> > > > >=sys-libs/zlib-1.2.11-r1 minizip |
124 |
> > > > |
125 |
> > > > +# required by www-misc/monitorix-3.9.0::gentoo |
126 |
> > > > +# required by monitorix (argument) |
127 |
> > > > +>=net-analyzer/rrdtool-1.6.0-r1 perl graph |
128 |
> > > |
129 |
> > > If you accept the above portage will emerge |
130 |
> > > net-analyzer/rrdtool-1.6.0-r1 with USE flags 'perl' and 'graph' |
131 |
> > > enabled. This change seems to be required by www-misc/monitorix for |
132 |
> > > some functionality of rrdtool (e.g. graphing) it needs.> > |
133 |
> > > > I can zap it or merge it or skip it. It looks like the emerge was |
134 |
> > > > successful, so, why should I do anything? |
135 |
> > > > |
136 |
> > > > $ rrdtool |
137 |
> > > > RRDtool 1.6.01.6.0 Copyright by Tobias Oetiker <tobi@×××××××.ch> |
138 |
> > > |
139 |
> > > Successful against what criteria? If monitorix needs/wants it to be |
140 |
> > > compiled so in order to perform graphing, it may not work until you've |
141 |
> > > enabled these USE flags and re-emerged (more successfully this time) |
142 |
> > > rrdtool. |
143 |
> > > |
144 |
> > > > I would have thought that emerge would pend until I'd agreed to the |
145 |
> > > > override. But, it apparently went ahead and installed. So what's |
146 |
> > > > required |
147 |
> > > > still? What will be different once I make the merge to zz-autounmask? |
148 |
> > > |
149 |
> > > If the changes in USE flags were hardcoded in the ebuild, because |
150 |
> > > without them an insurmountable conflict would arise, I expect portage |
151 |
> > > would refuse to emerge and complain of a hard block [B]. |
152 |
> > > |
153 |
> > > -- |
154 |
> > > Regards, |
155 |
> > > Mick |
156 |
|
157 |
|
158 |
-- |
159 |
Regards, |
160 |
Mick |