| 1 |
On Tue, 10 May 2005 22:19:27 -0500 Brian Harring <ferringb@g.o> |
| 2 |
wrote: |
| 3 |
| On Tue, May 10, 2005 at 09:54:33PM +0100, Ciaran McCreesh wrote: |
| 4 |
| > Is there a standard way of handling testing for utility-type |
| 5 |
| > eclasses? For versionator I currently have a |
| 6 |
| > __versionator__test_blah function included in the eclass (source |
| 7 |
| > versionator.eclass works, it doesn't have any portage-specific |
| 8 |
| > code), but this is going to get a bit messy when I add in another |
| 9 |
| > few dozen tests... |
| 10 |
| > |
| 11 |
| > Maybe a simple test harness could be added as an option for the new |
| 12 |
| > eclass / elib setup? |
| 13 |
| Elaborate on the tests... |
| 14 |
|
| 15 |
Best example I can give are the kind of thing that's in versionator |
| 16 |
already. The tests in the updated version in bug 87157 are probably |
| 17 |
better than the ones in the tree... |
| 18 |
|
| 19 |
-- |
| 20 |
Ciaran McCreesh : Gentoo Developer (Vim, Shell tools, Fluxbox, Cron) |
| 21 |
Mail : ciaranm at gentoo.org |
| 22 |
Web : http://dev.gentoo.org/~ciaranm |
Archives