From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 2ACE6139694 for ; Mon, 10 Jul 2017 14:23:12 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 6CB7A21406B; Mon, 10 Jul 2017 14:23:05 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 2237F214001 for ; Mon, 10 Jul 2017 14:23:04 +0000 (UTC) Received: from [IPv6:2001:44b8:4197:2800:a37a:5ec1:db17:1e49] (2001-44b8-4197-2800-a37a-5ec1-db17-1e49.static.ipv6.internode.on.net [IPv6:2001:44b8:4197:2800:a37a:5ec1:db17:1e49]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: kensington) by smtp.gentoo.org (Postfix) with ESMTPSA id 376B1341810 for ; Mon, 10 Jul 2017 14:23:02 +0000 (UTC) Subject: [gentoo-dev] Re: About adding a *warning* to remind maintainers to check for new PYTHON_COMPAT values References: <1499684650.24824.6.camel@gentoo.org> <7fc662d1-f65f-cb84-01dd-532bdc6e7182@gentoo.org> <1499687023.24824.12.camel@gentoo.org> <20170711013534.11cb860f@katipo2.lan> To: gentoo-dev@lists.gentoo.org From: Michael Palimaka Message-ID: Date: Tue, 11 Jul 2017 00:22:58 +1000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 In-Reply-To: <20170711013534.11cb860f@katipo2.lan> Content-Type: text/plain; charset=windows-1252 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Archives-Salt: 200f0345-e03f-4025-8141-8c43b7c5bf38 X-Archives-Hash: 848705e545949fc72828092c4f1e7b77 On 07/10/2017 11:35 PM, Kent Fredric wrote: > On Mon, 10 Jul 2017 13:43:43 +0200 > Pacho Ramos wrote: > >> Yes, but it's similar as the cases when we need to fix our packages >> to work with a newer library they depend on. In this case it would be >> even easier as we can have multiple python versions and switch to the >> newer one for testing while going back to the stable one (if >> preferred) later. >> > > I'm starting to think we need a collection of QA scripts in a repo > somewhere, optimized for symlinking into /etc/portage/hooks/install/ > > And make it standard practice for: > > - Gentoo Devs to have those scripts > - Tinderboxers' to have those scripts > > That's going to be the only way we can get these warnings in ways > *developers* will see them, but: > > 1. Won't needlessly clutter stable users systems > 2. Won't produce loads of ebuild bumps that do waves of metadata > updates for things that don't affect end users. > > Presently the only things *like* this require hard-coded QA logic into > portage itself, which, while useful, pulls us back to the whole problem > where it might affect users, and becomes tightly coupled to portage's > release cycle. > > We could however make things simpler, and have a package that installs > these QA hacks into the hooks dir for us, and then it would be a matter > of simply installing them via opt-in In addition to the checks that are bundled, Portage already natively supports custom post-install QA checks in: * /usr/local/lib/install-qa-check.d * /usr/lib/install-qa-check.d * $REPO/metadata/install-qa-check.d It's just a matter of someone writing and shipping them. I've been very slowly preparing a collection based on the common type of tinderboxing bugs that are filed and porting parts of lintian, but I haven't finished yet.