From: Francesco Riosa <francesco@pnpitalia.it>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Tests for eclasses
Date: Sat, 14 May 2005 13:21:55 +0200 [thread overview]
Message-ID: <4285DF53.9060008@pnpitalia.it> (raw)
In-Reply-To: <20050510215433.5b90c716@snowdrop>
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 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?
>
>
>
ciaranm, would you commit it ?
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-05-14 11:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-10 20:54 [gentoo-dev] Tests for eclasses Ciaran McCreesh
2005-05-11 0:36 ` Ciaran McCreesh
2005-05-11 10:39 ` Francesco Riosa
2005-05-11 12:12 ` Aaron Walker
2005-05-11 3:19 ` Brian Harring
2005-05-11 15:46 ` Ciaran McCreesh
2005-05-23 8:45 ` Francesco Riosa
2005-05-23 8:52 ` Ciaran McCreesh
2005-05-14 11:21 ` Francesco Riosa [this message]
2005-05-14 18:40 ` Ciaran McCreesh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4285DF53.9060008@pnpitalia.it \
--to=francesco@pnpitalia.it \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox