-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Francesco Riosa wrote: > could it be the other way around ? Use the saved and if it fail try to > use the current? > > Reason for this is that otherwise you need to maintain in the tree code > to un-merge very old packages, needlessy bloating the current, plus > experience teach this is very error prone. > > There is a problem however with this approach, you can't fix bug where > the (original ebuild) exit code is "success" but the behaviour is "damn > bugged".
It gets a little messy if we have to check exit codes like that. If pkg_prerm() fails with the saved ebuild/eclasses, then we substitute everything that we can from the live tree and then try again? What about if pkg_prerm() succeeds with the saved ebuild/eclasses, but then pkg_postrm() fails? I suppose we would substitute everything that we can from the live tree at that point. It's a little messy but I guess we can do that if that's how people think it should behave. Anyway, portage-2.1.2 is nearing a final release and it may be the stable version of portage for 2007.0, so it might be a good idea to make it start saving eclasses.tbz2 for installed packages now (even if it doesn't actually use them for anything). I imagine that it will just be a bzipped tarball containing an "eclass" directory with all of the inherited eclasses inside. Zac -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFTTa9/ejvha5XGaMRAmI+AJ0URJ9FEssxQsT/qEvnRqJkUppQBACg1Isa 76JGdGN7DzmFBwBndd6DujA= =dsoy -----END PGP SIGNATURE----- -- [email protected] mailing list
