From: Peter Fein <pfein@pobox.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] testing during emerge?
Date: Fri, 11 Apr 2003 10:13:04 -0500 [thread overview]
Message-ID: <20030411101304.383e5fbe.pfein@pobox.com> (raw)
In-Reply-To: <200304101847.56952.george@gentoo.org>
On Thu, 10 Apr 2003 18:47:56 -0700
George Shapovalov <george@gentoo.org> wrote:
> Well, I guess this can easily be done via another USE flag. I see no reason to
> do any changes to portage or anything, just the ebuilds (at least some of
> them) should be done to allow optionally run included test suites.
I was thinking that some portage/ebuild infrastructure might save some code
repitition. The problem seems more complicated than doing "make test || die" -
especially when you get in to expected failures, etc.. Maybe I'm making this more difficult than it needs to be. ;)
> And then, I just want to emphasize that this should be optional, as not that
> many people will be happy about forced increase in compile time. Thus I think
> this is the case where use flag is an ideal approach.
Choice is good.
> Then I guess you help can be in the form of submitting diff's against the
> ebuilds, where you would like to add optional tests ;). The tests should
> apparently be run from within src_compile() (and die on failure).
I'm willing to take a crack at this, but getting maintainers on board seems useful as it's a natural extension of the configure/build process.
> Though I somehow feel, that this issue has a potential to grow into a long
> discussion thread, what seems to be quite popular lately. So you might want
> to hold off for a few days to see how this turns out in the end..
You don't need to tell me not to work twice. ;)
--Pete
> On Thursday 10 April 2003 18:33, Peter Fein wrote:
> > Sorry if this has been covered before...
> >
> > So I recently got hit by the gcc/pentium4 bug, as described here:
> > http://forums.gentoo.org/viewtopic.php?t=43373
> >
> > Why this was particularly annoying is that Python (and lots of other progs)
> > include test suites which can catch these sort of things. While this is a
> > non-issue for binary distros, being able to run a test suite ("make test"
> > or whatever) as part of an emerge would be pretty useful. My ebuild
> > experience is somewhat limited (though it doesn't look that hard) though
> > I've done a good bit of work in Python. I'd be willing to help out on such
> > a project, if there's interest.
> >
> > --Pete
>
>
> --
> gentoo-dev@gentoo.org mailing list
>
>
--
Peter Fein
pfein@pobox.com
773-575-0694
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2003-04-11 15:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-11 1:33 [gentoo-dev] testing during emerge? Peter Fein
2003-04-11 1:47 ` George Shapovalov
2003-04-11 14:28 ` Dan Armak
2003-04-11 15:13 ` Peter Fein [this message]
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=20030411101304.383e5fbe.pfein@pobox.com \
--to=pfein@pobox.com \
--cc=gentoo-dev@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