Is there a standard way of handling testing for utility-type eclasses? For versionator I currently have a __versionator__test_blah function included in the eclass (source versionator.eclass works, it doesn't have any portage-specific code), but this is going to get a bit messy when I add in another few dozen tests...
Maybe a simple test harness could be added as an option for the new eclass / elib setup? -- Ciaran McCreesh : Gentoo Developer (Vim, Shell tools, Fluxbox, Cron) Mail : ciaranm at gentoo.org Web : http://dev.gentoo.org/~ciaranm
pgpDhsznXPsMw.pgp
Description: PGP signature
