From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-user+bounces-149049-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
by finch.gentoo.org (Postfix) with ESMTP id 04CC41381F3
for <garchives@archives.gentoo.org>; Mon, 29 Jul 2013 14:56:44 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id EAA13E0A91;
Mon, 29 Jul 2013 14:56:38 +0000 (UTC)
Received: from mail-wi0-f169.google.com (mail-wi0-f169.google.com [209.85.212.169])
(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id BCD9FE0A7E
for <gentoo-user@lists.gentoo.org>; Mon, 29 Jul 2013 14:56:37 +0000 (UTC)
Received: by mail-wi0-f169.google.com with SMTP id f14so974693wiw.0
for <gentoo-user@lists.gentoo.org>; Mon, 29 Jul 2013 07:56:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=from:reply-to:to:subject:date:user-agent:references:in-reply-to
:mime-version:content-type:content-transfer-encoding:message-id;
bh=ZxXBqePsIqyOC9l9V2sE1neJtzCcQmvrC7MvUnDcBrc=;
b=GkoKbwlXbjosTTpDINdgQ55ScvoBHcpULrZ2H85SKc0gZd1i4I306aozGdPB1dsaJz
MoUF7kMHSF/5iRdBm6HDtu6n893izK+nkmokRFzajCmio+xgljdtF8xmayBdwUAZGmRJ
ZrDN71Oc3pqEF+ZOkKVF97B4g0BYw9YbA1khMocX1bYhTW8FOQBTauboaUnxL6XlkOO1
AZcCsLfL/Q2aQGAHBZyELsNILqr3DHcZR19OliAEYdPfLGN3S8SUq9wI4YE45vwO59Qn
VnpUi12+49vFvuq9kMEpHfSpphEkrGOx72k2hHVS5J/zvBniHwOiZ5cEuS2Vg4jcPeqE
qUMQ==
X-Received: by 10.180.9.69 with SMTP id x5mr2949268wia.41.1375109796376;
Mon, 29 Jul 2013 07:56:36 -0700 (PDT)
Received: from dell_xps.localnet (230.3.169.217.in-addr.arpa. [217.169.3.230])
by mx.google.com with ESMTPSA id r6sm379718wiw.0.2013.07.29.07.56.34
for <gentoo-user@lists.gentoo.org>
(version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Mon, 29 Jul 2013 07:56:35 -0700 (PDT)
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Creating binary packages before updating them
Date: Mon, 29 Jul 2013 15:56:30 +0100
User-Agent: KMail/1.13.7 (Linux/3.8.13-gentoo; KDE/4.10.4; x86_64; ; )
References: <kt5j1c$kna$1@ger.gmane.org> <kt5klj$96u$1@ger.gmane.org> <51F65B10.5090108@gmail.com>
In-Reply-To: <51F65B10.5090108@gmail.com>
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
Content-Type: multipart/signed;
boundary="nextPart2029588.ZR4F2XvvjF";
protocol="application/pgp-signature";
micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <201307291556.32684.michaelkintzios@gmail.com>
X-Archives-Salt: 7e270086-9182-419d-9249-5c0768450cc0
X-Archives-Hash: a1808c736cbc63a7a39541a703b3985c
--nextPart2029588.ZR4F2XvvjF
Content-Type: Text/Plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
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.
> >>>=20
> >>> 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?
> >>=20
> >> 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.
> >>=20
> >> You can process all existing packages with
> >>=20
> >> quickpkg \*/\*
> >>=20
> >> I suspect you could also do this be defining a custom src_setup functi=
on
> >> in /etc/portage/bashrc - FEATURES=3D"buildpkg" is a lot less hassle un=
less
> >> you are really tight on disk space.
> >=20
> > 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.
>=20
> 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.
>=20
> I have that set here and it should do what you want in the long run. It
> just does it differently.
>=20
> Dale
It's been so long since I've used this feature I forgot how binary packages=
=20
are purged. Do they stay in $PKGDIR for ever, until something like eclean=
=20
deals with them, or can you specify (where?) to only keep the last n versio=
ns?
=2D-=20
Regards,
Mick
--nextPart2029588.ZR4F2XvvjF
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
iQEcBAABAgAGBQJR9oKgAAoJELAdA+zwE4YeldUH/iaAst9OIxh1WGMlFWhnVmH1
q5HDq+tMWQ/6naCS8YP/oosmo9ugxpyNiyRhgbRJn34/PuLLIi0XJffk21xjJpBb
cRP3PcmLt5Po0iScjFy6wh7/JopZa00S+wCeqkUo+jqadr2YCUEjc/eau17Ri7TN
cybpWVuFZVmt/HLR17JR1rbgrCYcG5LoRRVXtJdj/8wRwRAiK/gkG3Ci+aSszhf4
ce0Gw3EoKlC0cVb/GPV0eheyOevAOL3HeynPDhFe1Yf0jIJvdQl1UQNrQdtpvBDm
9CXFWesVb6yeA2T8RGYeDp7OKCPu1a3EOIGQIMNWbpFrDCjptmmyhJAz03USoGQ=
=UB3M
-----END PGP SIGNATURE-----
--nextPart2029588.ZR4F2XvvjF--