[gentoo-user] Creating binary packages before updating them

[gentoo-user] Creating binary packages before updating them

[Nikos Chantziaras]

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?

Re: [gentoo-user] Creating binary packages before updating them

[Raffaele BELARDI]

On 07/29/2013 01:18 PM, 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?

Isn't it --buildpkg?

Re: [gentoo-user] Creating binary packages before updating them

[Tanstaafl]

On 2013-07-29 7:18 AM, Nikos Chantziaras <realnc@gmail.com> 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?

Add FEATURES="buildpkg" to make.conf...

[gentoo-user] Re: Creating binary packages before updating them

[Nikos Chantziaras]

On 29/07/13 14:24, Raffaele BELARDI wrote:
> On 07/29/2013 01:18 PM, 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?
>
> Isn't it --buildpkg?

Unfortunately, no.  --buildpkg only builds binary packages after they've 
been replaced already.  I want binary packages of the packages that are 
being replaced instead.

Re: [gentoo-user] Creating binary packages before updating them

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]

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.


-- 
Neil Bothwick

If ignorance is bliss, you must be orgasmic.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[gentoo-user] Re: Creating binary packages before updating them

[Nikos Chantziaras]

On 29/07/13 14:27, Tanstaafl wrote:
> On 2013-07-29 7:18 AM, Nikos Chantziaras <realnc@gmail.com> 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?
>
> Add FEATURES="buildpkg" to make.conf...

This creates packages for everything and only *after* they've been 
merged.  I need to create tbzs for packages that are being replaced, and 
only when I want to.

[gentoo-user] Re: Creating binary packages before updating them

[Nikos Chantziaras]

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.

Re: [gentoo-user] Re: Creating binary packages before updating them

[Dale]

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

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!

Re: [gentoo-user] Creating binary packages before updating them

[Peter Humphrey]

On Monday 29 Jul 2013 07:27:23 Tanstaafl wrote:
> On 2013-07-29 7:18 AM, Nikos Chantziaras <realnc@gmail.com> 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?
> 
> Add FEATURES="buildpkg" to make.conf...

That way you'll gradually build up a /usr/portage/packages directory with a 
package for everything installed. Or if you don't want to wait months for 
that:

# emerge -eB world

when your box is not too busy. My KDE amd64 box (not ~amd64, for the most 
part) has 918 packages installed and the .../packages directory occupies 2GB.

-- 
Regards,
Peter

Re: [gentoo-user] Re: Creating binary packages before updating them

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 2335 bytes --]

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

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

Re: [gentoo-user] Re: Creating binary packages before updating them

[Dale]

[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]

Mick wrote:
> On Monday 29 Jul 2013 13:07:44 Dale wrote:
>>
>>
>> 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?
>

As far as I know, eclean is the only way to clean them.  It's a manual
thing but I guess one could script it and do a cron job.

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!


[-- Attachment #2: Type: text/html, Size: 1744 bytes --]

Re: [gentoo-user] Re: Creating binary packages before updating them

[Alan McKinnon]

On 29/07/2013 16:56, Mick wrote:
> 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?
> 

2 easy methods:

rm
eclean packages

eclean works the same as for distfiles, it can delete binpkgs that are
no longer in the tree, that you don't have installed, or all previous
versions of what you do have installed.

But they never automagically get purged, the admin has to do it
(manually or by cron or whatever0

-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] Creating binary packages before updating them

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 520 bytes --]

On Mon, 29 Jul 2013 15:21:59 +0100, Peter Humphrey wrote:

> > Add FEATURES="buildpkg" to make.conf...  
> 
> That way you'll gradually build up a /usr/portage/packages directory
> with a package for everything installed. Or if you don't want to wait
> months for that:
> 
> # emerge -eB world

It isn't necessary to recompile everything just to build packages of
them, quickpkg will do that.


-- 
Neil Bothwick

One difference between a man and a machine is that a machine is quiet
when well oiled.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: Creating binary packages before updating them

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 868 bytes --]

On Mon, 29 Jul 2013 14:45:53 +0300, Nikos Chantziaras wrote:

> > I suspect you could also do this by 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.

Checking the portage man page, I see you can set up per-package bashrc
files. Once you get the first one scripted, you can just copy/symlink it
for every package you want a per-emerge package for.

The exact implementation is left as an exercise for the reader :)


-- 
Neil Bothwick

Always be sincere even if you don't mean it.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Creating binary packages before updating them

[Alan McKinnon]

On 29/07/2013 21:46, Neil Bothwick wrote:
> On Mon, 29 Jul 2013 15:21:59 +0100, Peter Humphrey wrote:
> 
>>> Add FEATURES="buildpkg" to make.conf...  
>>
>> That way you'll gradually build up a /usr/portage/packages directory
>> with a package for everything installed. Or if you don't want to wait
>> months for that:
>>
>> # emerge -eB world
> 
> It isn't necessary to recompile everything just to build packages of
> them, quickpkg will do that.
> 
> 


Just make sure that quickpkg does what you want with config files...

been there, done that, made the mistakes :-)

-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] Creating binary packages before updating them

[Volker Armin Hemmann]

[-- Attachment #1: Type: text/plain, Size: 942 bytes --]

or you can make yourself a wrapper script that, depending on an option
calls quickpkg before emerge or not. Even better, not calling emerge, but
ebuild - with the different steps, and before merging into filesystem, call
quickpkg.


2013/7/29 Alan McKinnon <alan.mckinnon@gmail.com>

> On 29/07/2013 21:46, Neil Bothwick wrote:
> > On Mon, 29 Jul 2013 15:21:59 +0100, Peter Humphrey wrote:
> >
> >>> Add FEATURES="buildpkg" to make.conf...
> >>
> >> That way you'll gradually build up a /usr/portage/packages directory
> >> with a package for everything installed. Or if you don't want to wait
> >> months for that:
> >>
> >> # emerge -eB world
> >
> > It isn't necessary to recompile everything just to build packages of
> > them, quickpkg will do that.
> >
> >
>
>
> Just make sure that quickpkg does what you want with config files...
>
> been there, done that, made the mistakes :-)
>
> --
> Alan McKinnon
> alan.mckinnon@gmail.com
>
>
>

[-- Attachment #2: Type: text/html, Size: 1545 bytes --]

Re: [gentoo-user] Re: Creating binary packages before updating them

[Mike Gilbert]

On Mon, Jul 29, 2013 at 7:29 AM, Nikos Chantziaras <realnc@gmail.com> wrote:
> On 29/07/13 14:24, Raffaele BELARDI wrote:
>>
>> On 07/29/2013 01:18 PM, 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?
>>
>>
>> Isn't it --buildpkg?
>
>
> Unfortunately, no.  --buildpkg only builds binary packages after they've
> been replaced already.  I want binary packages of the packages that are
> being replaced instead.
>
>

It is probably easier/safer to just use FEATURES=buildpkg and then do
emerge -e world. From that point forward, you will have a binpkg for
every version of every package you ever install.

[gentoo-user] Re: Creating binary packages before updating them

[Nikos Chantziaras]

On 30/07/13 01:18, Mike Gilbert wrote:
> On Mon, Jul 29, 2013 at 7:29 AM, Nikos Chantziaras <realnc@gmail.com> wrote:
>> On 29/07/13 14:24, Raffaele BELARDI wrote:
>>>
>>> On 07/29/2013 01:18 PM, 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?
>>>
>>>
>>> Isn't it --buildpkg?
>>
>>
>> Unfortunately, no.  --buildpkg only builds binary packages after they've
>> been replaced already.  I want binary packages of the packages that are
>> being replaced instead.
>
> It is probably easier/safer to just use FEATURES=buildpkg and then do
> emerge -e world. From that point forward, you will have a binpkg for
> every version of every package you ever install.

Thanks everyone, though this isn't what I need or want.  I'll stick with 
quickpkg.