Re: Packaging mauve for debian

[Grzegorz Prokopski <gadek at debian dot org>]

W liście z czw, 17-10-2002, godz. 17:30, Tom Tromey pisze: 
> You should really use the existing build environment.
> One problem with precompiling Mauve is that then you need a new
> mechanism for deciding what tests to run.  Mauve was built (some would
> say mistakenly) to decide what tests to run at build time.
I was thinking about it and here's my solution.
I think I package the source of mauve into binary package.
Then I create script which unpacks it to /tmp/$secure_name/
./configures it and runs. then it removes /tmp/$secure_name
if not told otherwise (for ex. by specifing temp dir by hand)

I think it would be the best thing that can be done w/o
digging deeply into mauve's nature.

It's not just a normal-user package and I think such approach
can be used for this, _sepcific_ package.

Or maybe you'd have some other proposals?

Regards

				Grzegorz B. Prokopski

Attachment: signature.asc
Description: PGP signature