public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] tests
Date: Sun, 6 May 2007 04:39:43 -0400	[thread overview]
Message-ID: <200705060439.44141.vapier@gentoo.org> (raw)
In-Reply-To: <20070502211248.749c6b21@snowflake>

[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]

On Wednesday 02 May 2007, Ciaran McCreesh wrote:
> Mike Frysinger <vapier@gentoo.org> wrote:
> > On Tuesday 01 May 2007, Piotr Jaroszyński wrote:
> > > There was some discussion about forcing/not forcing tests in
> > > EAPI-1, but there was clearly no compromise.
> >
> > the compromise was that requiring in spec is wrong ... default
> > handling of tests is up to the package manager / profiles / teams
>
> That's a lousy solution.

all ive said is that it's better than what you proposed: making src_test 
mandatory.  that is not nor ever will be a viable solution.

> *Something* needs to change. There are several 
> solutions better than the current situation; the question is whether
> anyone can find one that is perfect rather than one that is merely a
> lot better.

the only feasible thing that should go into EAPI is to change the *default* 
behavior of src_test from not being run to being run ... thus all existing 
methods for controlling test behavior will continue to work the same
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 827 bytes --]

  reply	other threads:[~2007-05-06  8:42 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-01 13:08 [gentoo-dev] tests Piotr Jaroszyński
2007-05-01 13:24 ` Josh Sled
2007-05-01 13:32   ` Ciaran McCreesh
2007-05-01 15:50 ` Alec Warner
2007-05-01 16:04 ` Daniel Gryniewicz
2007-05-01 16:23   ` Vlastimil Babka
2007-05-01 17:18 ` Maurice van der Pot
2007-05-01 17:35   ` Ciaran McCreesh
2007-05-01 19:53     ` Maurice van der Pot
2007-05-01 20:05       ` Piotr Jaroszyński
2007-05-02  5:58         ` Rémi Cardona
2007-05-02  6:53           ` Danny van Dyk
2007-05-01 21:52       ` Josh Saddler
2007-05-01 22:31         ` Stephen Bennett
2007-05-01 22:28           ` Josh Saddler
2007-05-01 22:47             ` Piotr Jaroszyński
2007-05-01 23:08         ` Ciaran McCreesh
2007-05-01 23:06       ` Ciaran McCreesh
2007-05-01 17:58   ` Piotr Jaroszyński
2007-05-01 19:24 ` Rémi Cardona
2007-05-01 20:10   ` Jure Varlec
2007-05-01 22:06     ` Robin H. Johnson
2007-05-01 20:25 ` [gentoo-dev] tests Piotr Jaroszyński
2007-05-01 23:32 ` [gentoo-dev] tests Marius Mauch
2007-05-01 23:46   ` Daniel Gryniewicz
2007-05-01 23:55     ` Ciaran McCreesh
2007-05-02  0:34       ` Brian Harring
2007-05-02 11:52         ` Ciaran McCreesh
2007-05-02  0:08     ` Robin H. Johnson
2007-05-02  0:12     ` Stephen Bennett
2007-05-02  1:51       ` Daniel Gryniewicz
2007-05-02  6:49         ` Danny van Dyk
2007-05-02 11:56         ` Ciaran McCreesh
2007-05-01 23:56   ` Ciaran McCreesh
2007-05-02 10:54   ` Philipp Riegger
2007-05-02 20:05 ` Mike Frysinger
2007-05-02 20:12   ` Ciaran McCreesh
2007-05-06  8:39     ` Mike Frysinger [this message]
2007-05-05 21:17 ` [gentoo-dev] tests Ryan Hill
2007-05-06  4:27   ` Alistair John Bush

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=200705060439.44141.vapier@gentoo.org \
    --to=vapier@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