From: Alexis Ballier <aballier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Providing consistent means to enable tests requiring Internet access
Date: Fri, 28 Apr 2017 11:22:16 +0200 [thread overview]
Message-ID: <20170428112216.52a36067@gentoo.org> (raw)
In-Reply-To: <CAJ0EP40kxo-ej3OwQWY+Ubg0PysDAty1VgesugHG97S7CFTN4w@mail.gmail.com>
On Thu, 27 Apr 2017 17:57:30 -0400
Mike Gilbert <floppym@gentoo.org> wrote:
> On Thu, Apr 27, 2017 at 5:42 PM, Alexis Ballier <aballier@gentoo.org>
> wrote:
> > On Thu, 27 Apr 2017 16:14:13 +0200
> > Michał Górny <mgorny@gentoo.org> wrote:
> >
> >> b. those tests can easily be enabled, and that fact is recorded
> >> in the installed package metadata,
> >>
> >> c. the flag can easily be used in RESTRICT="" constraint to easily
> >> disable all the tests.
> >
> >
> > I see that as a rather important disadvantage. Why would we want to
> > record that in VDB ?
> >
> >
> >> What do you think? Any other ideas?
> >
> > why not simply a new RESTRICT value ?
> >
>
> How would a new RESTRICT value help? There's no way for a
> user/developer to disable a RESTRICT setting unless it is declared
> behind a USE flag.
>
What I was thinking is RESTRICT="internet-tests" letting PM skip
src_test if users disabled it, just like RESTRICT=test. But this fails
when one only wants to skip part of the tests.
next prev parent reply other threads:[~2017-04-28 9:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-27 14:14 [gentoo-dev] [RFC] Providing consistent means to enable tests requiring Internet access Michał Górny
2017-04-27 21:42 ` Alexis Ballier
2017-04-27 21:57 ` Mike Gilbert
2017-04-28 9:22 ` Alexis Ballier [this message]
2017-04-28 5:07 ` Michał Górny
2017-04-28 9:19 ` Alexis Ballier
2017-04-28 13:25 ` Kent Fredric
2017-04-28 13:37 ` Michał Górny
2017-04-28 14:00 ` 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=20170428112216.52a36067@gentoo.org \
--to=aballier@gentoo.org \
--cc=gentoo-dev@lists.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