From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id BDBFC1381F3 for ; Mon, 29 Jul 2013 15:30:49 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 90F7EE0ADE; Mon, 29 Jul 2013 15:30:40 +0000 (UTC) Received: from mail-gh0-f173.google.com (mail-gh0-f173.google.com [209.85.160.173]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 91F46E0AD9 for ; Mon, 29 Jul 2013 15:30:39 +0000 (UTC) Received: by mail-gh0-f173.google.com with SMTP id g16so1771128ghb.4 for ; Mon, 29 Jul 2013 08:30:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:x-enigmail-version:content-type; bh=H0SLRYujOcNkEYeG24HruCgBfcXAC/GAdKQK5RVXCRo=; b=FDf930GuoYbTYolQQ1X4jbmWAZWRyFtuUnAP+o0JviicIjZLiLlDrgoqPHDaSNp+y0 WMzF5Eex1l37m9P7nmhcuwfB2We2R+kqIrH//tlnIAxBcqAdKTDiLuRNABF3uS0LKSAl w5oGLW5+tN/fv7uPn4zRdgC4UMV3scTX1xK+jjeDoqP3ssC8TA1Qfcsd2CYCCVX7l6JZ 6/qu3rAI+jOEKzijGlvxquuG/YhSIfIX8wSVWJ4kqJ6Vn3wLt2dn2RZXkEAeOkCgPNjY wl3svHL8MIr15wL7dyqYliqO3ztFXGadneA2wOXzbTf9wOiTBCVLmYPXprVo69FIV0M8 jY5Q== X-Received: by 10.236.138.195 with SMTP id a43mr26952493yhj.61.1375111838548; Mon, 29 Jul 2013 08:30:38 -0700 (PDT) Received: from [192.168.2.5] (adsl-65-0-122-60.jan.bellsouth.net. [65.0.122.60]) by mx.google.com with ESMTPSA id n4sm19887792yhk.5.2013.07.29.08.30.37 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 29 Jul 2013 08:30:37 -0700 (PDT) Message-ID: <51F68A9C.4050304@gmail.com> Date: Mon, 29 Jul 2013 10:30:36 -0500 From: Dale User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:22.0) Gecko/20100101 Firefox/22.0 SeaMonkey/2.19 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: Creating binary packages before updating them References: <51F65B10.5090108@gmail.com> <201307291556.32684.michaelkintzios@gmail.com> In-Reply-To: <201307291556.32684.michaelkintzios@gmail.com> X-Enigmail-Version: 1.5.2 Content-Type: multipart/alternative; boundary="------------020100010205040700020205" X-Archives-Salt: 57ecd075-cb37-46a9-9241-2e233f0fb447 X-Archives-Hash: cb0fac60bd18c661f9c857200b61d3cb This is a multi-part message in MIME format. --------------020100010205040700020205 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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! --------------020100010205040700020205 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit 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!

--------------020100010205040700020205--