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.mckin...@gmail.com >> >> > -- Alan McKinnon alan.mckin...@gmail.com
