1 |
El mar, 22-07-2014 a las 07:39 +0000, Martin Vaeth escribió: |
2 |
> Pacho Ramos <pacho@g.o> wrote: |
3 |
> > |
4 |
> > Maybe this could be solved by having two kinds of revisions: |
5 |
> > - One would rebuild all as usually (for example, -r1...) |
6 |
> > - The other one would only regenerate VDB and wouldn't change the |
7 |
> > installed files (for example, -r1.1) |
8 |
> |
9 |
> I made the same suggestion already on the corresponding bug |
10 |
> https://bugs.gentoo.org/show_bug.cgi?id=516612#c33 |
11 |
> without any response. |
12 |
|
13 |
Just CCed :) |
14 |
|
15 |
> |
16 |
> It seems to me that this could avoid the problem of useless |
17 |
> recompilation and would allow fine-graining of the issue by the |
18 |
> ebuild maintainer (if not the maintainer of the ebuild, who else |
19 |
> should be able to decide whether recompilation might be |
20 |
> necessary to handle certain exceptions?) |
21 |
> and simultaneously allow to revbump even on presumably |
22 |
> tiny dependency changes. |
23 |
> |
24 |
> I still have not seen an argument against this idea. |
25 |
> |
26 |
> Of course, this would need an EAPI bump and could only be used |
27 |
> for packages which are (or switch to(?)) this new EAPI, so a few |
28 |
> (core) packages which should stay EAPI=0 for a long time |
29 |
> are excluded from this for still quite a while. |
30 |
> But apart from that few exceptions...? |
31 |
> |
32 |
> |
33 |
|
34 |
Also, this could be a benefit in the long term if we need to spread any |
35 |
changes to VDB in the future. |