Re: tarball should include m4-files needed for autoconf

Hallo

> I agree that putting the m4 files in CVS is retarded, but I think
> adding them to the built tarball is easy and wouldn't negatively
> affect the CVS repository or the build and release process of
> mjpegtools.
I can live with that version too.
Like having a empty directory (called missing_m4) we just fill for the 
final build on the "developers" system with the missing sdl.m4, glib.m4 
and gtk.m4 files. Maybe we add a file that tells the people that want to 
make a package from the mjpegtools which files they should add. And why 
we have that directory.

But has anybody a answer which version of the sdl.m4 file I should add ? 
The on that comes with the Suse 9.3 where I build the package. or the 
one that comes with the Suse 10.2. (I have a debian system here to I 
could use that one also)

BTW: We do only have the problem with the tar file ?
Or do we also have that problem with the source RPM package ?
We should not have that problem with the rpm package because that one is 
compiled with SDL and GTK support, so you need that packages.

If nothing happens (to me) I will make next weekend a RC2, and put it 
online.

auf hoffentlich bald,

Berni the Chaos of Woodquarter

Email: [email protected]
www: http://www.lysator.liu.se/~gz/bernhard

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV