public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Proposal for changes for the next EAPI version
Date: Tue, 17 May 2016 07:42:51 -0400	[thread overview]
Message-ID: <CAGfcS_nKGsX1kbYx=g8VNzidLces0DR+0ejtVD8pzS+rYvjwQg@mail.gmail.com> (raw)
In-Reply-To: <CAK23ojTx3rvkYsLPJW7cLz2j5z9GbXsHmKP=tNNbTfJ=5Kv9TA@mail.gmail.com>

On Tue, May 17, 2016 at 7:25 AM, Pallav Agarwal
<pallavagarwal07@gmail.com> wrote:
> Because we are already expecting an arch tester to conduct tests for the
> package. And knowing what to test is something I expect to come more
> easily from the maintainer.
>

It would come even more easily from upstream.  My point is that
upstream obviously doesn't consider it a priority, since if they did
they'd be already supplying automated build scripts and we'd already
be using them in the test phase.  Maintainers generally don't consider
them a priority either, since I imagine many existing upstream build
scripts aren't implemented, and when they don't exist maintainers
generally do not provide test plans.

Again, I'm not objecting to the creation of this feature.  I just
think that it is unlikely to have a large impact on how things get
done except perhaps for a couple packages or projects.  For those
packages/projects that do adopt this I'm sure there will be some real
benefits.

I'd also suggest having some way to break out short vs long tests.  It
might be beneficial to users to be able to run the tests on their own
systems and not just limit this to arch testing.  Obviously users are
going to be less likely to want to run test scripts that take hours to
run.  Due to the nature of Gentoo it is unlikely that the environment
used for testing by the AT is identical to the environment the
packages will be run in.  I'm not negating the value of testing prior
to stabilization, but I don't agree that it completely takes the place
of testing at time of installation and if we have automated test
scripts, why not make them available to users?

Of course, that would suggest that there is a potential benefit to be
had from putting this into an EAPI.  My suggestion would be to try to
design this so that it would be appropriate for a future EAPI, but
defer considering it for an EAPI until we see the feature getting
enough use/demand to warrant this.

-- 
Rich


  reply	other threads:[~2016-05-17 11:43 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-16 12:43 [gentoo-dev] Proposal for changes for the next EAPI version Pallav Agarwal
2016-05-16 16:38 ` Luis Ressel
2016-05-17  7:37   ` Pallav Agarwal
2016-05-17  8:02     ` Kent Fredric
2016-05-17  8:46       ` Tobias Klausmann
2016-05-17  9:15         ` Kent Fredric
2016-05-17 10:57           ` Rich Freeman
2016-05-17 11:25             ` Pallav Agarwal
2016-05-17 11:42               ` Rich Freeman [this message]
2016-05-17 10:01         ` Pallav Agarwal
2016-05-17 11:26           ` Michael Orlitzky
2016-05-17 11:29             ` Ciaran McCreesh
2016-05-18  8:18               ` [gentoo-dev] " Duncan
2016-05-17 13:53     ` [gentoo-dev] " M.B.
2016-05-17 14:02       ` Brian Dolbec
2016-05-17 15:34     ` Luis Ressel
2016-05-17 16:05       ` Sébastien Fabbro
2016-05-17 16:42         ` Rich Freeman
2016-05-18  0:14         ` Kent Fredric
2016-05-18  0:35           ` M. J. Everitt
2016-05-18  0:44             ` Kent Fredric
2016-05-18  0:48               ` M. J. Everitt

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='CAGfcS_nKGsX1kbYx=g8VNzidLces0DR+0ejtVD8pzS+rYvjwQg@mail.gmail.com' \
    --to=rich0@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