Recently, Portage changed the order of running the pkg_* phases on upgrades and downgrades from the traditional
* pkg_preinst the new version * merge the new version * pkg_postinst the new version * pkg_prerm the old version * unmerge the old version * pkg_postrm the old version to * pkg_preinst the new version * merge the new version * pkg_prerm the old version * unmerge the old version * pkg_postrm the old version * pkg_postinst the new version Of course, this breaks backwards compatibility, leading to broken ebuilds and broken systems, and demonstrates a complete failure to comprehend the concept of a stable EAPI. On the other hand, we don't care about breakage and we don't have a stable EAPI. The new ordering is consistent with that for reinstalls, as well as probably being more useful in general (since, if the package will ultimately end up installed, the pkg_postinst will be run last and can undo any deregistration that may have been performed by pkg_postrm). So the question is: do we want to make the change for Exheres? _______________________________________________ Exherbo-dev mailing list [email protected] http://lists.exherbo.org/mailman/listinfo/exherbo-dev
