| 1 |
On 30/07/13 01:18, Mike Gilbert wrote: |
| 2 |
> On Mon, Jul 29, 2013 at 7:29 AM, Nikos Chantziaras <realnc@×××××.com> wrote: |
| 3 |
>> On 29/07/13 14:24, Raffaele BELARDI wrote: |
| 4 |
>>> |
| 5 |
>>> On 07/29/2013 01:18 PM, Nikos Chantziaras wrote: |
| 6 |
>>>> |
| 7 |
>>>> Normally, when I'm about to update an important package, I back it up |
| 8 |
>>>> first using quickpkg. I'm often in a situation though where many |
| 9 |
>>>> important packages are being updated in a world update. Normally, I |
| 10 |
>>>> have to manually quickpkg every one of them. |
| 11 |
>>>> |
| 12 |
>>>> Is there a way to tell emerge to do this on its own? That is, create |
| 13 |
>>>> binary packages of every package that it is replacing? |
| 14 |
>>> |
| 15 |
>>> |
| 16 |
>>> Isn't it --buildpkg? |
| 17 |
>> |
| 18 |
>> |
| 19 |
>> Unfortunately, no. --buildpkg only builds binary packages after they've |
| 20 |
>> been replaced already. I want binary packages of the packages that are |
| 21 |
>> being replaced instead. |
| 22 |
> |
| 23 |
> It is probably easier/safer to just use FEATURES=buildpkg and then do |
| 24 |
> emerge -e world. From that point forward, you will have a binpkg for |
| 25 |
> every version of every package you ever install. |
| 26 |
|
| 27 |
Thanks everyone, though this isn't what I need or want. I'll stick with |
| 28 |
quickpkg. |
Archives