From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] question about binhost's
Date: Mon, 17 Nov 2014 23:54:27 +0200 [thread overview]
Message-ID: <546A6E93.6050909@gmail.com> (raw)
In-Reply-To: <20141117214623.GA3253@asterix>
On 17/11/2014 23:46, Michael Mair-Keimberger wrote:
> On Mon, Nov 17, 2014 at 11:27:08PM +0200, Alan McKinnon wrote:
>> On 17/11/2014 23:01, Michael Mair-Keimberger wrote:
>>> Hi list,
>>>
>>> I was setting up an binhost recently and i couldn't found any
>>> information how to keep old builds.
>>> Usually, for example a newer version of tcpdump gets build, the old
>>> build will be deleted. Only different slots were keeped. However, I
>>> want to keep these old builds but I haven't found an option for that.
>>>
>>> Is it even possible to keep these? If not, anyone know why? if it's not
>>> possible there must be a reason and i couldn't think of anyone...
>>>
>>
>> short answer:
>> emerge -b
>>
>> long answer:
>> read "man emerge". All of it. Gotchas await.
>
> Well, the man page doesn't describe why it can't keep old builds...
> (don't know what you referring too)
>
> I do know `emerge -b` creates binary packages, but i orginally asked for
> a way to keep older versions of binary packages.
You can't because emerge does not work that way[1].
If you want to keep the contents of an installed package:
a. use binpkgs to create an archive of the package at the time it is
built (not at the time is is about to be replaced)
b. Manually run quickpkg on packages you are interested in before
emerging them
[1] Unless Zac added this feature since the last time I read the man
pages. Won't be the first time a new feature sneaked in without a user
noticing :-)
>
> Example:
>
> emerge -b =net-analyzer/tcpdump-4.5.1-r1
> - binary package for tcpdump-4.5.1-r1 gets created
> emerge -b =net-analyzer/tcpdump-4.6.2
> - binary package for tcpdump-4.6.2 gets created AND tcpdump-4.5.1-r1
> gets deleted
>
> However, I want to keep tcpdump-4.5.1-r1 if possible.
>
> Is there a way? Simply emerge -b isn't sufficiency.
>
>>
>> --
>> Alan McKinnon
>> alan.mckinnon@gmail.com
>>
>>
>
--
Alan McKinnon
alan.mckinnon@gmail.com
next prev parent reply other threads:[~2014-11-17 21:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 21:01 [gentoo-user] question about binhost's Michael Mair-Keimberger
2014-11-17 21:27 ` Alan McKinnon
2014-11-17 21:46 ` Michael Mair-Keimberger
2014-11-17 21:54 ` Alan McKinnon [this message]
2014-11-17 21:32 ` thegeezer
2014-11-17 21:46 ` Alan McKinnon
2014-11-17 21:57 ` Matti Nykyri
2014-11-17 21:55 ` Michael Mair-Keimberger
2014-11-17 22:14 ` Neil Bothwick
2014-11-18 6:45 ` Mick
2014-11-18 7:46 ` wraeth
2014-11-18 8:41 ` Neil Bothwick
2014-11-18 19:47 ` Michael Mair-Keimberger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=546A6E93.6050909@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox