Le jeudi 01 avril 2010 à 03:18 -0700, Brian Harring a écrit : > On Thu, Apr 01, 2010 at 12:10:20PM +0200, Gilles Dartiguelongue wrote: > > jumping on the train here, but who said PM would not feed proper data to > > pkg_pretend so it would behave like the DEPEND were already built. Could > > some guy involved in a PM development tell us about how this would be > > handled ? > > Good idea, but not really viable. The only scenario where this would > work cleanly is in has_version checks which most of the time should be > blockers/deps anyways.
That's indeed the only thing I was thinking of > Basically, you want the PM to lie to the ebuild in some fashion. > Since pkg_pretend is free form, it's effectively impossible to cover > the scenarios it could check on- consider checking the kernel > config/version, or checking the active jvm/python version. except the kernel will not change during the upgrade, unless you reboot in the middle of the upgrade but I would expect the PM to recompute pkg_pretend in resume. > Some of those can sort of be handled, but it requires a lot of custom > code (code that has to change as the tools involved change) to pull it > off. > > As said, good idea, but it was ruled out due to it being techically > infeasible considering the gains. Since I have little insight on the rest I will trust whatever decision has been taken. -- Gilles Dartiguelongue <e...@gentoo.org> Gentoo
