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 832D11381F3 for ; Thu, 11 Apr 2013 19:03:30 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 10AA3E0B37; Thu, 11 Apr 2013 19:03:29 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 7CE57E0B37 for ; Thu, 11 Apr 2013 19:03:28 +0000 (UTC) Received: from mail-qc0-f180.google.com (mail-qc0-f180.google.com [209.85.216.180]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mattst88) by smtp.gentoo.org (Postfix) with ESMTPSA id 9AE5833DE91 for ; Thu, 11 Apr 2013 19:03:27 +0000 (UTC) Received: by mail-qc0-f180.google.com with SMTP id b40so841266qcq.25 for ; Thu, 11 Apr 2013 12:03:25 -0700 (PDT) X-Received: by 10.49.39.162 with SMTP id q2mr9567406qek.17.1365707005959; Thu, 11 Apr 2013 12:03:25 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-catalyst@lists.gentoo.org Reply-to: gentoo-catalyst@lists.gentoo.org MIME-Version: 1.0 Received: by 10.49.28.41 with HTTP; Thu, 11 Apr 2013 12:03:05 -0700 (PDT) In-Reply-To: <516706A3.6000500@gentoo.org> References: <513A2F19.5040203@gentoo.org> <6472ad55830b40f838356a1b083b3815a4112358.1362768301.git.wking@tremily.us> <20130309121023.GE26574@odin.tremily.us> <20130411170941.GA14224@odin.tremily.us> <516706A3.6000500@gentoo.org> From: Matt Turner Date: Thu, 11 Apr 2013 12:03:05 -0700 Message-ID: Subject: Re: [gentoo-catalyst] Binary package dependencies and update_seed To: gentoo-catalyst@lists.gentoo.org Content-Type: text/plain; charset=ISO-8859-1 X-Archives-Salt: 066d73b1-b656-4031-990c-12bae2de7f6f X-Archives-Hash: bdd4569ad9668f0b398fe7fb013dc23e On Thu, Apr 11, 2013 at 11:53 AM, Rick "Zero_Chaos" Farina wrote: >> Not sure this is the way to go. I'll have to think through the >> implications. Consider your stage1 build dies with some stupid tree >> breakage that you can fix in your portage snapshot and restart the >> stage build. This is going to cause your stage to rebuild everything. >> >> Wouldn't disabling the use of binary packages during the seed stage >> update fix this? >> >> > I'm not sure I'd call rebuilding it every time a "fix" when you just > rejected deleting the bad packages and rebuilding ONCE. I'm not sure what you mean. Updating the seed stage should only ever happen once. If that fails and you don't have binary packages to fall back to on restarting, I think that's an okay price to pay. Especially since it happens early enough in the process and avoids potential problems that are only noticed at the beginning of stage2. Oh, and if updating the seed stage fails... it was only rebuilding gcc dependencies anyway. That's not so bad at all. (I don't care about custom update commands and isn't something that we can fix) > As I said, the only proper fix is to update the toolchain to EAPI5. We > could live in the dark ages forever, but I really don't think it helps > anyone. That seems like a potentially good long term goal, but isn't something that we can force through.