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 8126B1397EC for ; Wed, 19 Aug 2015 20:22:17 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DCAFE142C4; Wed, 19 Aug 2015 20:22:06 +0000 (UTC) Received: from mail-lb0-f181.google.com (mail-lb0-f181.google.com [209.85.217.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 5993B14289 for ; Wed, 19 Aug 2015 20:22:05 +0000 (UTC) Received: by lbcbn3 with SMTP id bn3so10789046lbc.2 for ; Wed, 19 Aug 2015 13:22:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:in-reply-to:message-id:references:user-agent :mime-version:content-type; bh=aA9CoPMQASYTjJLW377pOJfpl7gnzq94HzJKClRSDyY=; b=qO/6ezfxsoqkbcHbwmBPQt+mCBvRdxI/5697elbhT6BwxtXEZEGfZ48BBbLM8Y3Xp/ UP0icXKe73X+98mmik0G3PVpx2m2tVPSalRWAime5FD7vTX9o3VBVAa7dN/KwKS5Qjl7 uvOdiwlyikVFikOcrXF7PRDy27qS4PFMRsR9rAA+TMCTTFGxvjNwlbwM+5aEMJwAyCWM KFlA061c7bHG/2R+ZPgW30l2mRw9pVKnQJ2JD+3CusGNZu8QoCdtO6fZwztW85rhOR9h tpio5OvdufCM3Wmd5s9ie0d8NrBJcpwc0b0Y8/aXOROQMah1/LTrKAPHE8BZqEIXKYbx KHVw== X-Received: by 10.112.67.65 with SMTP id l1mr13431203lbt.86.1440015723549; Wed, 19 Aug 2015 13:22:03 -0700 (PDT) Received: from gentoo-tp.home (77-253-30-38.adsl.inetia.pl. [77.253.30.38]) by smtp.gmail.com with ESMTPSA id w9sm517890laj.21.2015.08.19.13.22.01 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 19 Aug 2015 13:22:02 -0700 (PDT) Date: Wed, 19 Aug 2015 22:22:02 +0200 (CEST) From: Jeremi Piotrowski X-X-Sender: jeremi@gentoo-tp.localdomain To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: !!!! In-Reply-To: <55D4E317.5020204@gmail.com> Message-ID: References: <55D38D15.3040800@verizon.net> <55D3F471.8070904@cox.net> <201508192055.18533.michaelkintzios@gmail.com> <20150819195842.GB734@apio.adsroot.itcs.umich.edu> <55D4E317.5020204@gmail.com> User-Agent: Alpine 2.20 (LNX 67 2015-01-07) 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 Content-Type: text/plain; charset=US-ASCII X-Archives-Salt: 3deb284d-9dae-414a-9a43-246fcff4a263 X-Archives-Hash: 398c372b9181419b4d4cf3b22efb43e7 On Wed, 19 Aug 2015, Alan McKinnon wrote: > On 19/08/2015 21:58, Alec Ten Harmsel wrote: > > On Wed, Aug 19, 2015 at 08:55:16PM +0100, Mick wrote: > >> On Wednesday 19 Aug 2015 10:28:48 Jeremi Piotrowski wrote: > >>> Smart live rebuild only deals with live ebuilds. How would it help in this > >>> case? > >> > >> Anyone cares to explain what is a "live ebuild"? > >> > >> Then I may be able to understand what @smart-live-rebuild may be useful for. > >> :-/ > >> > >> -- > >> Regards, > >> Mick > > > > A "live ebuild" is an ebuild that pulls the code to build straight from > > whatever version control the developers are using, so you always have > > the latest and greatest. > > > > Alec > > > > > they usually have version number -9999 > portage has no way of knowing if the repository the package comes from has been updated without fetching the sources and this is done during the merge process. So portage has no knowledge of the state of live-ebuild packages prior to starting a merge - it doesn't know if they have been updated upstream, so it does nothing to them during normal updates. To update them you can use the set @live-rebuild. But this causes live packages to be unconditionally rebuilt even if they haven't changed. Smart-live-rebuild deals with this by updating the repositories and then only re-emerging packages that have been changed.