From: Jerry V. <je...@ma...> - 2002-02-20 20:25:57
|
>> Is gmake an option ? > > Yes - or preferably autoconf followed by gmake. But they don't have the > same support for Perlish type stuff (dependency checking, installing > modules) as Perl's MakeMaker. > I have a lot of expirence with gmake, not so much with autoconf. For me, MakeMaker is out because the uninstall doesn't work. Could the install create a xmltv-only directory hierarchy say: xmltv-0.4.1/bin doc perllib (whatever else is needed) Everything installed in bin could have the #!perl line modified to add -I/usr/local/xmltv-0.4.1/perllib as part of the installation. That way the user can have /usr/local/xmltv-XX/bin in their PATH and everything works. This is pretty easy to build in a simple Makefile. The only system utilities required I suspect is probably a 'install' which we could substitute with out own simple perl script if we wanted. We could release a windows-binary tar ball and say a /usr/local/xmltv-X.X.X tar ball for easy installation. As for dependencies, we could pretty easily roll our own "checkpackages" script that verifies required packages and versions. This doesn't take much. And cvs users, well nothing says they can't be forced to do: % cvs co xmltv % rm -rf /usr/local/xmltv-cvs % make install INSTALLDIR=/usr/local/xmltv-cvs less error prone if the install target fails if INSTALLDIR exists. jerry |