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