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 1430E1387FD for ; Fri, 6 Jun 2014 23:46:08 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C4CCCE0B0F; Fri, 6 Jun 2014 23:46:03 +0000 (UTC) Received: from mail-we0-f175.google.com (mail-we0-f175.google.com [74.125.82.175]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 6690EE0AF2 for ; Fri, 6 Jun 2014 23:46:02 +0000 (UTC) Received: by mail-we0-f175.google.com with SMTP id p10so3576731wes.34 for ; Fri, 06 Jun 2014 16:46:01 -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:content-type:content-transfer-encoding; bh=Tr6FqCrVkXXqVkn56ETYmhPMmMfSk0tlHvFJazBvl8o=; b=0VsK1ob3IpCksV1L81WqHdwya9B4AToXDyWkcNN4Q+XiaVRHGp9ovqRYw3/xKVVFPJ YrfsjZB8Pj5TPV+51N0dmtb2JZq99iv1WWPbRZ1Rgsa8kx/uSLGqmNDJ0AN9Q9ldRbNJ zYjjKKcI0x+++idl/G5wuSJtQzWUm9xJWaHwHxd9MPLjZHC8ClF6hA4fy9yKK4LdzNtl Q8DEL/Bl4+QwVt81+UcEi3Jm4JQoOOWGhzTaDVgsPtvzT4orxcQWGqT4ZefKZPWUbsLW Osi1T2HEvL3z9VtSSpzOsaAZz0Xy53Vq5A2Y55M0vPos/2fulXtVjCm6YNGypdOOiyCe 0H9g== X-Received: by 10.14.211.66 with SMTP id v42mr1622677eeo.1.1402098361018; Fri, 06 Jun 2014 16:46:01 -0700 (PDT) Received: from [172.20.0.40] (196-215-51-239.dynamic.isadsl.co.za. [196.215.51.239]) by mx.google.com with ESMTPSA id w48sm26135220eel.9.2014.06.06.16.45.59 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 06 Jun 2014 16:46:00 -0700 (PDT) Message-ID: <5392528A.9020003@gmail.com> Date: Sat, 07 Jun 2014 01:45:14 +0200 From: Alan McKinnon User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 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] Use Flags and Updating References: <006001cf741f$db183a40$9148aec0$@gmail.com> <537B3FE9.8050207@gmail.com> <007001cf7420$4f8a8f90$ee9faeb0$@gmail.com> <537B413D.1090209@gmail.com> <537CAF05.9010805@gmail.com> <20140522021037.GA4074@badass.gateway.2wire.net> <20140522095448.76d13462@marcec> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Archives-Salt: b2e991c8-416e-4845-8c4b-ee2cf0eb854b X-Archives-Hash: 668ddc52b22dae5b296f0ab1f5706a16 On 06/06/2014 12:44, Rich Freeman wrote: > On Thu, May 22, 2014 at 3:54 AM, Marc Joliet wrote: >> I think nowadays one would prefer --keep-going, which automatically resumes on >> failure (and recomputes the dependency tree!), and prints a list of failed >> packages when it's finished. However its output is more verbose than just "ok" >> and "failed" (it'll print the build.log if it's only one package, IIRC). > > Hmm, after using this script for some time I found a problem with this > approach. If you use --buildpkgonly and ---keep-going then emerge > won't build a single thing if anything in the list is missing a > build-time dependency. The script I posted will try to emerge > everything individually so at least some of the packages will be > compiled. > > That seems like a bug in --buildpkgonly. If you use it with > --keep-going it should at least compile the packages that aren't > missing build-time options. I'll file that as a bug if it isn't > already there... I don't think it's a bug, it's more like a difference in interpretation. >From the man page: --buildpkgonly (-B) Creates binary packages for all ebuilds processed without actually merging the packages. This comes with the caveat that all build-time dependencies must already be emerged on the system. --keep-going [ y | n ] Continue as much as possible after an error. When an error occurs, dependencies are recalculated for remaining pack‐ ages and any with unsatisfied dependencies are automati‐ cally dropped. Also see the related --skipfirst option. So, decisions about --buildpkgonly are made at the start of an emerge and --keep-going kicks in only when an error occurs at the end, and the former must have higher precedence than the latter. It doesn't make sense to expect portage to change it's behaviour about it's initial decisions just because you also have an entirely unrelated option set that is only a convenience in the event of a build failure. That seems to me too much of an unexpected side effect -- Alan McKinnon alan.mckinnon@gmail.com