Ciaran McCreesh wrote:
On Tue, 10 May 2005 22:19:27 -0500 Brian Harring [EMAIL PROTECTED]
wrote:
| On Tue, May 10, 2005 at 09:54:33PM +0100, Ciaran McCreesh wrote:
| Is there a standard way of handling testing for utility-type
| eclasses? For versionator I currently have a
|
On Tue, 10 May 2005 22:19:27 -0500 Brian Harring [EMAIL PROTECTED]
wrote:
| On Tue, May 10, 2005 at 09:54:33PM +0100, Ciaran McCreesh wrote:
| Is there a standard way of handling testing for utility-type
| eclasses? For versionator I currently have a
| __versionator__test_blah function included
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
On Tue, May 10, 2005 at 09:54:33PM +0100, Ciaran McCreesh wrote:
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
