public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Josh Saddler <nightmorph@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] tests
Date: Tue, 01 May 2007 15:28:42 -0700	[thread overview]
Message-ID: <4637BF1A.1010309@gentoo.org> (raw)
In-Reply-To: <20070501233111.5fd54b7b@maya>

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

Stephen Bennett wrote:
> On Tue, 01 May 2007 14:52:30 -0700
> Josh Saddler <nightmorph@gentoo.org> wrote:
> 
>> anyway, on the subject of tests...as others have covered the *first*
>> time this was discussed on the lists, mandatory tests being run every
>> time the user installs a package? no. oh hell no. we don't seem to do
>> that much with the packages in our tree now, do we?
> 
> Care to turn that into a reasoned argument rather than what appears to
> be a knee-jerk reaction?

Not a knee jerk reaction, just a strong one. One of the key reasons why
mandatory tests were not desired was the fact that sometimes much more
stuff will be installed than what you'd normally get. Exhibit A:
robbat2's message just sent on diradm that normally just needs openldap
with USE=minimal, but building for tests requires all of openldap,
samba, etc.

I'd like to think we aren't in the practice of forcing users to install
cruft on their systems. If you need more examples from the last thread,
assuming you don't still have local archives, I could scrounge 'em from
gmane I suppose, though we're both equally capable of typing in search
phrases. The tests subject wasn't brought up that long ago, either.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-05-01 22:31 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 [this message]
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
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=4637BF1A.1010309@gentoo.org \
    --to=nightmorph@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