1 |
Well, I guess this can easily be done via another USE flag. I see no reason to |
2 |
do any changes to portage or anything, just the ebuilds (at least some of |
3 |
them) should be done to allow optionally run included test suites. |
4 |
And then, I just want to emphasize that this should be optional, as not that |
5 |
many people will be happy about forced increase in compile time. Thus I think |
6 |
this is the case where use flag is an ideal approach. |
7 |
|
8 |
Then I guess you help can be in the form of submitting diff's against the |
9 |
ebuilds, where you would like to add optional tests ;). The tests should |
10 |
apparently be run from within src_compile() (and die on failure). |
11 |
Though I somehow feel, that this issue has a potential to grow into a long |
12 |
discussion thread, what seems to be quite popular lately. So you might want |
13 |
to hold off for a few days to see how this turns out in the end.. |
14 |
|
15 |
George |
16 |
|
17 |
|
18 |
On Thursday 10 April 2003 18:33, Peter Fein wrote: |
19 |
> Sorry if this has been covered before... |
20 |
> |
21 |
> So I recently got hit by the gcc/pentium4 bug, as described here: |
22 |
> http://forums.gentoo.org/viewtopic.php?t=43373 |
23 |
> |
24 |
> Why this was particularly annoying is that Python (and lots of other progs) |
25 |
> include test suites which can catch these sort of things. While this is a |
26 |
> non-issue for binary distros, being able to run a test suite ("make test" |
27 |
> or whatever) as part of an emerge would be pretty useful. My ebuild |
28 |
> experience is somewhat limited (though it doesn't look that hard) though |
29 |
> I've done a good bit of work in Python. I'd be willing to help out on such |
30 |
> a project, if there's interest. |
31 |
> |
32 |
> --Pete |
33 |
|
34 |
|
35 |
-- |
36 |
gentoo-dev@g.o mailing list |