Brian Jones wrote:
> Actually have two better thought out ideas.
>
> 1. Use dist-hook to cp -r java and gnu directories into the
> distribution. This should keep 'make' from compiling anything in lib.
> 2. Change the if MAINTAINER_BUILD section to encompass compiling the
> Java files and creating glibj.zip.
>
> Anyone have a preference? The first option is affected by timestamps
> after the end user untars the package.
The problem with Option 2 is that it requires that the user have JavaDeps
installed in order to build because the maintainer build options rebuilds
the .deps file, which is something few people will want to do.
Option 1 should work, but will make the distribution larger than it needs to
be by a very large amount. If we include the classes, but not the zip file,
then the user needs to have zip installed in order to build, which not
everyone with a Unix box does. (We should be checking for that in
configure, BTW). I would prefer not to do that until will have our own jar
utility. Including both compiled classes and a glibj.zip file is a lot of
space. (The glibj.zip file itself is already about half of our distribution
size).
Maybe we could have a configure option that would simply skip the lib
directory build if the user doesn't want to rebuild the Java classes. This
could be on or off by default, depending on what we like. Of course we have
to make sure the lib directory gets included in the "install" target.
--
Aaron M. Renn ([EMAIL PROTECTED]) http://www.urbanophile.com/arenn/
