I was recently checking out the new Entropy package manager, having wished to upgrade a Sabayon 1.x box that was too slow to conveniently compile updates (p3-500/186MB/12g), and noticed that the order of operations that are performed when installing packages with equo seems to have a potential issue with it.
I am familiar with ebuilds and portage, but not so much with entropy. With emerge, when you upgrade a package, the actions are roughly as follows:
- Code: Select all
grab archive
unzip to tempspace
build
install into a temp filesystem
copy the completed image to the live filesystem
With entropy it isn't as transparent, but its output looks like this:
- Code: Select all
pkg_prerm()
pkg_postrm()
grab the archive
unpack it to tempspace
copy it to the live filesystem
What if you decide to update X11, and you lose your network connection?
Does it rip out the old package before downloading the new one, or do those calls not do what they do in portage? Iirc pkg_prerm() isn't called during an emerge'd update. It makes sense to remove the old files to avoid the buildup of clutter, but shouldn't we wait till we have a good copy of the new one?
Anyway, perhaps i need to rtfm a bit better, but i didn't want to test that and risk messing up my box, as it has no way to boot except from main hard disk.
Let me know if I've helped, or if I don't understand the process in equo.
Cheers,
Mordjah
