From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Proposal for changes for the next EAPI version
Date: Wed, 18 May 2016 08:18:43 +0000 (UTC) [thread overview]
Message-ID: <pan$7d583$752c824b$2848c134$164d2857@cox.net> (raw)
In-Reply-To: 20160517122936.0f0e10f9@snowflex
Ciaran McCreesh posted on Tue, 17 May 2016 12:29:36 +0100 as excerpted:
> On Tue, 17 May 2016 07:26:03 -0400 Michael Orlitzky <mjo@gentoo.org>
> wrote:
>> We already have "emerge --config" which is expected to be run after the
>> install process has completed, so I don't think that this is too much
>> of a stretch. Maybe call the phase "pkg_test" analogous to "pkg_config"
>> and in contrast to "src_test" which runs within the working directory.
>> Then "emerge --test" could run it.
>
> For various technical reasons to do with the spec and package manglers
> sometimes using phase function names with the src_ or pkg_ stripped off,
> calling it that would be a huge pain.
What about something like gentoo_test, or more generically, distro_test?
That would also emphasize the difference between distro-level
functionality and integration testing (which if I'm reading correctly is
the proposal here) and upstream-level testing, via src_test.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2016-05-18 8:19 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 ` Duncan [this message]
2016-05-17 13:53 ` 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='pan$7d583$752c824b$2848c134$164d2857@cox.net' \
--to=1i5t5.duncan@cox.net \
--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