| 1 |
On 29/07/13 14:35, Neil Bothwick wrote: |
| 2 |
> On Mon, 29 Jul 2013 14:18:03 +0300, Nikos Chantziaras wrote: |
| 3 |
> |
| 4 |
>> Normally, when I'm about to update an important package, I back it up |
| 5 |
>> first using quickpkg. I'm often in a situation though where many |
| 6 |
>> important packages are being updated in a world update. Normally, I |
| 7 |
>> have to manually quickpkg every one of them. |
| 8 |
>> |
| 9 |
>> Is there a way to tell emerge to do this on its own? That is, create |
| 10 |
>> binary packages of every package that it is replacing? |
| 11 |
> |
| 12 |
> You could parse the emerge output to build a list of packages and pass |
| 13 |
> that to quickpkg. You could even do his as a script |
| 14 |
> in /etc/portage/postsync.d to have it done automatically, but the |
| 15 |
> simplest long term solution is to add buildpkg to FEATURES, then you |
| 16 |
> don't have to try to anticipate which packages you need to backup. |
| 17 |
> |
| 18 |
> You can process all existing packages with |
| 19 |
> |
| 20 |
> quickpkg \*/\* |
| 21 |
> |
| 22 |
> I suspect you could also do this be defining a custom src_setup function |
| 23 |
> in /etc/portage/bashrc - FEATURES="buildpkg" is a lot less hassle unless |
| 24 |
> you are really tight on disk space. |
| 25 |
|
| 26 |
Too big a hammer. I suppose the answer is just "no." I was hoping for |
| 27 |
some obscure emerge option that I wasn't seeing (happened before), like |
| 28 |
"--buildpkg-replaced" or something. I'll keep using quickpkg then. I |
| 29 |
only need this very rarely. |
Archives