This is the mail archive of the mailing list for the Mauve project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [GNU Crypto] Re: request for comments (long)

Hash: RIPEMD160

hello Mark,

On Saturday 14 December 2002 01:54, Mark Wielaard wrote:
> On Wed, 2002-12-11 at 10:27, Raif S. Naffah wrote:
> > ...putting
> > the test classes under the gnu.testlet folder,
> > amending the 'choose' script, and to use a
> > $(project_so) seem to do the job.  i'll wait and see if others
> > suggest different alternatives/ideas before deciding which way to
> > jump.
> But I don't like Mauves configury/setup magic. Note that I once made
> some scripts that make using Mauve simpler (when you have a GNU
> system with bash).
> See:
> If these seem useful to you then I can import them into Mauve.

i havent looked very closely, but i like the way the process is broken 
into atomic steps.

>... You
> can then just use Mauve as upstream provider of your testframework. I
> wouldn't worry to much about having two copies of those files in
> different CVS trees. Both Mauve and GNU Crypto see active development
> but both groups of developers know each other, or are sometimes even
> the same people :) And the basic framework doesn't change that much
> anyway...

fine.  i'll add the Mauve classes and scripts to the GNU Crypto CVS and 
intergate locally.  make check in GNU Crypto should then run the mauve 

Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Que du magnifique


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]