1 |
On Fri, 29 Aug 2014 15:30:29 +0000 |
2 |
Sven Vermeulen <swift@g.o> wrote: |
3 |
|
4 |
> [...] |
5 |
> |
6 |
> With this change, we implement the same end result (correctly labeled |
7 |
> files after installation) while removing the need for the DEPEND |
8 |
> dependency. After all, this was not a build-time dependency but a |
9 |
> "merge-time" one, which we abused a bit to make things work. |
10 |
> |
11 |
> With this change in place, we can now update the tree (at least, for |
12 |
> those packages that do not have other SELinux related dependency |
13 |
> requirements - those that link with libselinux still need it in |
14 |
> DEPEND of course) to remove the USE="selinux" conditional dependency |
15 |
> from DEPEND. |
16 |
> |
17 |
> Given the discussion on dynamic dependencies and so, I am thinking |
18 |
> about doing this as follows: |
19 |
> |
20 |
> 1. Create a tracker with separate bugs for every package where this |
21 |
> change can be made |
22 |
> 2. Give developers time to apply this (simple) change together with |
23 |
> whatever other changes they were planning. |
24 |
> 3. After 6 months or so, do the change myself (with revbump) |
25 |
> |
26 |
> [...] |
27 |
> |
28 |
> Is this a good approach to take? |
29 |
> |
30 |
> [...] |
31 |
|
32 |
|
33 |
LGTM; we should avoid unnecessary bumps & rebuilds for trivial changes, |
34 |
especially when a USE flag based dependency line is removed from DEPEND. |
35 |
|
36 |
-- |
37 |
With kind regards, |
38 |
|
39 |
Tom Wijsman (TomWij) |
40 |
Gentoo Developer |
41 |
|
42 |
E-mail address : TomWij@g.o |
43 |
GPG Public Key : 6D34E57D |
44 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D |