public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Diego Elio Pettenò" <flameeyes@flameeyes.eu>
To: "gentoo-dev@lists.gentoo.org" <gentoo-dev@lists.gentoo.org>
Cc: python@gentoo.org
Subject: Re: [gentoo-dev] Packages with optional test dependencies
Date: Sun, 6 Jan 2013 13:28:06 +0100	[thread overview]
Message-ID: <CAHcsgXSX8OdMvYcLLgf_DjGnBaLq_ebH+gqK+CFJYcA-BTUnxg@mail.gmail.com> (raw)
In-Reply-To: <20130106113842.03b42401@pomiocik.lan>

Go for a. The widest and more consistent the testing, the better.

Otherwise the day after tomorrow you'll get a bug from me that with
$foo installed, $bar fails tests.
Diego Elio Pettenò — Flameeyes
flameeyes@flameeyes.eu — http://blog.flameeyes.eu/


On Sun, Jan 6, 2013 at 11:38 AM, Michał Górny <mgorny@gentoo.org> wrote:
> Hello,
>
> There are some Python packages which have a bunch of optional tests
> utilizing external packages. For example, the dev-python/logilab-common
> runs a few additional tests if dev-python/egenix-mx-base is installed;
> if the package is not installed, it just skips those tests.
>
> Those tests can't be really considered 'heavy' or in any way suggesting
> use of an additional USE flag.
>
> Do you believe that the ebuilds should:
>
> a) depend on all optional test dependencies conditionally to USE=test,
>    therefore always requesting the widest (and consistent) testing,
>
> b) not depend on the optional test dependencies, resulting in less
>    dependencies for most users but also a bit inconsistent test
>    experience,
>
> c) put the optional test dependencies behind an additional USE flag?
>
> --
> Best regards,
> Michał Górny


  reply	other threads:[~2013-01-06 12:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-06 10:38 [gentoo-dev] Packages with optional test dependencies Michał Górny
2013-01-06 12:28 ` Diego Elio Pettenò [this message]
2013-01-06 12:50   ` hasufell
2013-01-06 12:56     ` Diego Elio Pettenò
2013-01-06 19:36       ` Matthew Thode
2013-01-07  2:03 ` [gentoo-dev] " Ryan Hill

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=CAHcsgXSX8OdMvYcLLgf_DjGnBaLq_ebH+gqK+CFJYcA-BTUnxg@mail.gmail.com \
    --to=flameeyes@flameeyes.eu \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=python@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