From: Luis Ressel <aranea@aixah.de>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proposal for changes for the next EAPI version
Date: Tue, 17 May 2016 17:34:18 +0200 [thread overview]
Message-ID: <20160517173418.168d2cba@gentp.lnet> (raw)
In-Reply-To: <CAK23ojQ-RadRH8a_=fiHB0crpZDEe-RQU5cu71URG1fDPHO97A@mail.gmail.com>
On Tue, 17 May 2016 13:07:43 +0530
Pallav Agarwal <pallavagarwal07@gmail.com> wrote:
> Tests run in src_test are provided by upstream, and does not
> guarantee that a package that has been merged will actually run on
> the system. If the maintainer could add a couple small scripts to
> check basic functionality of the merged package, it would make
> testing for arch testers much easier and reliable.
Automated post-merge tests sound kinda dangerous to me. And I don't
think there's any stipulation about src_test() only running
upstream-provided test suites. IMHO, src_test() would be a good place
for most of the maintainter-provided tests you have in mind.
Of course, there are some possible tests for which the src_test()
environment isn't suitable (because they're either interactive or
really need to run post-merge), I just don't expect there'd be many of
them. Therefore, I think we'd be better off providing such tests
out-of-band (test plans in the wiki), or perhaps stuffing them into
pkg_config().
Don't get me wrong, I'm not at all opposed to your idea of easing the
ATs' life, I'm just not convinced of the neccessity of EAPI changes. :)
--
Regards,
Luis Ressel
Luis Ressel <aranea@aixah.de>
GPG fpr: F08D 2AF6 655E 25DE 52BC E53D 08F5 7F90 3029 B5BD
next prev parent reply other threads:[~2016-05-17 15:34 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
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 [this message]
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=20160517173418.168d2cba@gentp.lnet \
--to=aranea@aixah.de \
--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