| 1 |
On Mon, Nov 17, 2014 at 11:27:08PM +0200, Alan McKinnon wrote: |
| 2 |
> On 17/11/2014 23:01, Michael Mair-Keimberger wrote: |
| 3 |
> > Hi list, |
| 4 |
> > |
| 5 |
> > I was setting up an binhost recently and i couldn't found any |
| 6 |
> > information how to keep old builds. |
| 7 |
> > Usually, for example a newer version of tcpdump gets build, the old |
| 8 |
> > build will be deleted. Only different slots were keeped. However, I |
| 9 |
> > want to keep these old builds but I haven't found an option for that. |
| 10 |
> > |
| 11 |
> > Is it even possible to keep these? If not, anyone know why? if it's not |
| 12 |
> > possible there must be a reason and i couldn't think of anyone... |
| 13 |
> > |
| 14 |
> |
| 15 |
> short answer: |
| 16 |
> emerge -b |
| 17 |
> |
| 18 |
> long answer: |
| 19 |
> read "man emerge". All of it. Gotchas await. |
| 20 |
|
| 21 |
Well, the man page doesn't describe why it can't keep old builds... |
| 22 |
(don't know what you referring too) |
| 23 |
|
| 24 |
I do know `emerge -b` creates binary packages, but i orginally asked for |
| 25 |
a way to keep older versions of binary packages. |
| 26 |
|
| 27 |
Example: |
| 28 |
|
| 29 |
emerge -b =net-analyzer/tcpdump-4.5.1-r1 |
| 30 |
- binary package for tcpdump-4.5.1-r1 gets created |
| 31 |
emerge -b =net-analyzer/tcpdump-4.6.2 |
| 32 |
- binary package for tcpdump-4.6.2 gets created AND tcpdump-4.5.1-r1 |
| 33 |
gets deleted |
| 34 |
|
| 35 |
However, I want to keep tcpdump-4.5.1-r1 if possible. |
| 36 |
|
| 37 |
Is there a way? Simply emerge -b isn't sufficiency. |
| 38 |
|
| 39 |
> |
| 40 |
> -- |
| 41 |
> Alan McKinnon |
| 42 |
> alan.mckinnon@×××××.com |
| 43 |
> |
| 44 |
> |
| 45 |
|
| 46 |
-- |
| 47 |
greetings |
| 48 |
Michael Mair-Keimberger |
Archives