tar.gz

[Jason Gunthorpe <jgg@gpu.srv.ualberta.ca>]

Scott,

The source tar.gz still doesn't have everything in it. I should be able to
unpack it on my 486 and run debian/rules build, I should not need libtool,
automake, autoconf or any of those other evil things (nor can I with this
bo system) 

You should run debian/rules Makefile.in and then fix the symlinks before
you build the tar.gz

Some of the things that must be in the tar (and not as symlinks) are
 configure
 */Makefile.in
 intl/

Again, I'd rather not have the things in CVS you put in, and I really
don't want all the Makefile.in's in CVS, I'd hope the packaging system is
flexable enough to let us do this :|

Right now my techinique for creating a good tar.gz for compilation on my
486 is this,

cvs export deity
cd deity
debian/rules Makefile.in
cd ..
tar -czhf deity.tar.gz deity

A different approach, adding a find script to the Makefile.in rule,
something like 
  find -type l -exec "cp {} {}.new; mv -f {}.new {}"
Would likely integrate best with the existing system ?

The goal here is to allow my 486 to take the tar.gz and compile it without
any external utilities.

If you can manage something like this then let me know and I will remove
those generated files from CVS (anything debian/rules Makefile.in produces
does not belong in cvs)

Now, in about a half hour I should have .13 compiled for bo :>

Thanks,
Jason


--
To UNSUBSCRIBE, email to deity-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org