From: Kristian Fiskerstrand <k_f@gentoo.org>
To: gentoo-dev@lists.gentoo.org, Kent Fredric <kentnl@gentoo.org>
Subject: Re: [gentoo-dev] About adding a *warning* to remind maintainers to check for new PYTHON_COMPAT values
Date: Mon, 10 Jul 2017 15:41:04 +0200 [thread overview]
Message-ID: <11785052-96d0-8193-bffa-7d4d12132712@gentoo.org> (raw)
In-Reply-To: <20170711013534.11cb860f@katipo2.lan>
[-- Attachment #1.1: Type: text/plain, Size: 816 bytes --]
On 07/10/2017 03:35 PM, Kent Fredric wrote:
> On Mon, 10 Jul 2017 13:43:43 +0200
> Pacho Ramos <pacho@gentoo.org> 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/
>
I might've read things too quickly, we're not talking a repoman check here?
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-07-10 13:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 11:04 [gentoo-dev] About adding a *warning* to remind maintainers to check for new PYTHON_COMPAT values Pacho Ramos
2017-07-10 11:12 ` Kristian Fiskerstrand
2017-07-10 11:43 ` Pacho Ramos
2017-07-10 13:35 ` Kent Fredric
2017-07-10 13:41 ` Kristian Fiskerstrand [this message]
2017-07-11 4:24 ` Brian Dolbec
2017-07-10 14:22 ` [gentoo-dev] " Michael Palimaka
2017-07-10 14:59 ` [gentoo-dev] " M. J. Everitt
2017-07-10 13:49 ` Rich Freeman
2017-07-10 16:55 ` William Hubbs
2017-07-10 17:25 ` Alexis Ballier
2017-07-11 11:21 ` Pacho Ramos
-- strict thread matches above, loose matches on Subject: below --
2017-07-10 17:37 Kent Fredric
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=11785052-96d0-8193-bffa-7d4d12132712@gentoo.org \
--to=k_f@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=kentnl@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox