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 2A4771381F3 for ; Fri, 19 Apr 2013 14:09:31 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9F306E0A91; Fri, 19 Apr 2013 14:09:30 +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 0E4C5E0A91 for ; Fri, 19 Apr 2013 14:09:29 +0000 (UTC) Received: from [192.168.1.4] (pool-71-245-176-92.pitbpa.fios.verizon.net [71.245.176.92]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: zerochaos) by smtp.gentoo.org (Postfix) with ESMTPSA id 1B8F833DF04 for ; Fri, 19 Apr 2013 14:09:29 +0000 (UTC) Message-ID: <517150A6.8020207@gentoo.org> Date: Fri, 19 Apr 2013 10:11:50 -0400 From: "Rick \"Zero_Chaos\" Farina" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130406 Thunderbird/17.0.5 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 To: gentoo-catalyst@lists.gentoo.org Subject: Re: [gentoo-catalyst] [PATCH 0/2] Blacklisting binary packages References: <20130309121023.GE26574@odin.tremily.us> In-Reply-To: X-Enigmail-Version: 1.6a1pre Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Archives-Salt: 460d4845-78cd-452c-aa7a-fd9216ea3b25 X-Archives-Hash: 489773b83cd3359694fcc68619b20baa -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/16/2013 03:42 PM, W. Trevor King wrote: > From: "W. Trevor King" > > The current approach to avoiding problems due to stale binary packages > with untracked ABI dependencies is to disable binpkg use during > troublesome sections of the build (e.g. seed updates). I think that a > cleaner solution would be to use a configurable spec option > blacklisting binpkgs for troublesome packages. For example, in a > stage1 with update_seed enabled, the Portage emerge (before the seed > update) has: > This needs to remain optional. I'm not going to nack a patch that some people may find useful but in my personal opinion this is a terrible solution that should not be used. We need to find a way to rebuild packages as needed (like EAPI 5) not force a rebuild everytime. - -ZC > … > removed '/usr/portage/packages/sys-devel/gcc-4.6.3.tbz2' > removed '/usr/portage/packages/sys-devel/gcc-config-1.7.3.tbz2' > emerge --quiet --usepkg --buildpkg --newuse --oneshot --nodeps --update sys-apps/portage > … > > During the seed update, the rest of the packages can use preexisting > binpkgs from earlier builds: > > … > >>> Emerging binary (1 of 17) sys-devel/gnuconfig-20121010 > >>> Installing (1 of 17) sys-devel/gnuconfig-20121010 > >>> Emerging binary (2 of 17) app-misc/mime-types-9 > >>> Installing (2 of 17) app-misc/mime-types-9 > >>> Emerging (3 of 17) sys-libs/timezone-data-2013a > >>> Installing (3 of 17) sys-libs/timezone-data-2013a > … > > I'm not sure yet why some packages (e.g. timezone-data) don't use the > prexisting binpkgs, even though they do exist: > > # ls packages/default/stage1-i686-2013.1/sys-libs/timezone-data-201* > packages/default/stage1-i686-2013.1/sys-libs/timezone-data-2012j.tbz2 > packages/default/stage1-i686-2013.1/sys-libs/timezone-data-2013a.tbz2 > > Later in the stage1 build, GCC is not installed from a binary package > (because this package was removed earlier): > > … > >>> Emerging binary (59 of 75) virtual/libc-0 for /tmp/stage1root/ > >>> Installing (59 of 75) virtual/libc-0 to /tmp/stage1root/ > >>> Emerging (60 of 75) sys-devel/gcc-4.6.3 for /tmp/stage1root/ > >>> Installing (60 of 75) sys-devel/gcc-4.6.3 to /tmp/stage1root/ > … > > I think this approach is cleaner because it: > > * Avoids problems we've already seen by blacklisting troublesome > packages. > * Allows you to reuse binary packages in the seed update stage, at the > cost of rebuilding gcc for your stage1root. > * Can be applied to any stage, so you don't get bitten by stale > binpkgs in stage2, etc. due to a snapshot update. > * Can be overridden by folks who know some blacklisted package will be > fine for their combination of seed, snapshot, and pkgcache. > > W. Trevor King (2): > spec: Add binpkg_blacklist option for troublesome packages > Revert "don't build packages during update_seed" > > modules/generic_stage_target.py | 4 +++- > targets/stage1/stage1-chroot.sh | 4 ++-- > targets/support/chroot-functions.sh | 5 +++++ > 3 files changed, 10 insertions(+), 3 deletions(-) > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRcVCmAAoJEKXdFCfdEflKD40QALjM2FK1L8wiwOQfuov9lMjZ WO2Qqmyx+asctFdtmpU9QV8GP3j68ZgFM3L/EhWSK0Fi3O9QiEiXXjdnSEH8iqF4 SsMvhCP2l05mBvYYrmpeHKCPmDLxGWB6ppMl/gNLzDOBNSk3VBwXILk5N2PN0QXz 3mnD48QeMd9sAVHKSFOoaY2SsHLQBR6WEH+wdq+bJmrwU8Y949hOksxm65itII+V 1jMpTo5hhBwrdqI04Uk0FQBnqF06zhm8eZO2HhbaFF4P5l+BCahFle+96T3X+ktZ NN4hw+5woxQOlPe8I2VX/4TdRtRvosdDkop3NnaBENKLu5pTqc0UsuRCw/DQolBg cgZJ3i6zYDjUTWCGq67nPVZtp3seS9hWJ75s/r8OKumpev+v4WDWt1XbY6UEChXg 4uTSD1lRLV+sXVNJthd5BGQb36mXiVM2muja2edOQfUHp1zxXJD3TklHXenDRw4w zioui7bsSi0ywI0ftdqff7M9XqlvogGQyduWswnPtoLOrDx32Z+UrAeAfihV9vHy ywhIb5n/EfBplARkSl+Q7QMemgrB2PEEIQJFLbZaGTHgAtTAwzcc3s5wB7KHIDvb RJ320R51FgWKgqqO1R6Bpqr2U6lUbE03uQDVlW82AWLM/WTRWgF+Fs18gHhvIo7n LOCMQuXVOV9HtRhYrfq9 =R5YJ -----END PGP SIGNATURE-----