| 1 |
Ciaran McCreesh wrote: |
| 2 |
|
| 3 |
>On Tue, 10 May 2005 21:54:33 +0100 Ciaran McCreesh <ciaranm@g.o> |
| 4 |
>wrote: |
| 5 |
>| Is there a standard way of handling testing for utility-type eclasses? |
| 6 |
>| For versionator I currently have a __versionator__test_blah function |
| 7 |
>| included in the eclass (source versionator.eclass works, it doesn't |
| 8 |
>| have any portage-specific code), but this is going to get a bit messy |
| 9 |
>| when I add in another few dozen tests... |
| 10 |
> |
| 11 |
>And along the same lines... Please test the updated versionator.eclass |
| 12 |
>that I have posted to [1]. I'd really rather find any bugs *before* it |
| 13 |
>hits the tree :) |
| 14 |
> |
| 15 |
>[1]: http://bugs.gentoo.org/show_bug.cgi?id=87157 |
| 16 |
> |
| 17 |
> |
| 18 |
> |
| 19 |
Nice and 30% faster here . Not tested version_sort() but I've already |
| 20 |
idea on where to use it. |
| 21 |
-- |
| 22 |
gentoo-dev@g.o mailing list |
Archives