> > A little while ago Neil turned me on to quickpkg. It sounds like a > > great way to protect yourself from the new package blues. Is anyone > > using it like that? What would be the best way to assure that your > > system always has a backup copy of your current version of a package > > available before emerging a new one? > > A more reliable method, assuming you have the drive space, is to add > buildpkg to FEATURES in make.conf. Then emerge will automatically build a > package when installing a package. It also means the package is verified, > because ebuild builds it then installs from the package it just built, not > the files in $PORTAGE_TMPDIR.
If I'm understanding it correctly, FEATURES="buildpkg" sounds less reliable for failed upgrade recovery. If you want to roll back to a previous version of a package, you're going to end up with what was originally installed, not what was working on your system right before the upgrade, right? Also, I tried to use quickpkg to protect me from any problems upgrading xorg and I ended up totally screwed. I quickpackaged my installed xorg, emerged the latest xorg, it wouldn't start, I tried to 'emerge -K xorg-x11', it said it was blocked by xorg-x11, I unmerged xorg-x11, it still said it was blocked, I tried to unmerge xorg-x11 again and it said it wasn't installed. It does sound like a portage problem instead of a quickpkg problem. I've finally gotten xorg working again thanks to a closed bug record, and let me tell you this: 1. don't emerge hardened xorg without dlloader 2. lynx doesn't work with gmail (predictable) - Grant > Neil Bothwick -- [email protected] mailing list
