On Monday 29 Jul 2013 13:07:44 Dale wrote: > Nikos Chantziaras wrote: > > On 29/07/13 14:35, Neil Bothwick wrote: > >> On Mon, 29 Jul 2013 14:18:03 +0300, Nikos Chantziaras wrote: > >>> Normally, when I'm about to update an important package, I back it up > >>> first using quickpkg. I'm often in a situation though where many > >>> important packages are being updated in a world update. Normally, I > >>> have to manually quickpkg every one of them. > >>> > >>> Is there a way to tell emerge to do this on its own? That is, create > >>> binary packages of every package that it is replacing? > >> > >> You could parse the emerge output to build a list of packages and pass > >> that to quickpkg. You could even do his as a script > >> in /etc/portage/postsync.d to have it done automatically, but the > >> simplest long term solution is to add buildpkg to FEATURES, then you > >> don't have to try to anticipate which packages you need to backup. > >> > >> You can process all existing packages with > >> > >> quickpkg \*/\* > >> > >> I suspect you could also do this be defining a custom src_setup function > >> in /etc/portage/bashrc - FEATURES="buildpkg" is a lot less hassle unless > >> you are really tight on disk space. > > > > Too big a hammer. I suppose the answer is just "no." I was hoping > > for some obscure emerge option that I wasn't seeing (happened before), > > like "--buildpkg-replaced" or something. I'll keep using quickpkg > > then. I only need this very rarely. > > If you set buildpkg in make.conf, you should already have a binary > stored. Example. You do a install with buildpkg in make.conf. From > that point on, when you do a update or new package install it stores a > binary package for everything. Then later on if you do a update and it > goes goofy, you can just use the -K option and it will restore the > binary it stored without compiling the package again. > > I have that set here and it should do what you want in the long run. It > just does it differently. > > Dale
It's been so long since I've used this feature I forgot how binary packages are purged. Do they stay in $PKGDIR for ever, until something like eclean deals with them, or can you specify (where?) to only keep the last n versions? -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
