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