[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Next question for help in Java packaging: beast-mcmc



Hi,

I would like to refresh my question about the problem I mentioned.
Here again a short summary:  At

   http://people.debian.org/~tille/packages/beast-mcmc-help-wanted/

you can find a source package of beast-mcmc.  All preconditions which
are not available in Debian are at

   http://people.debian.org/~tille/packages/figtree-help-wanted/

The problem:  Some of the wrapper scripts just find the jam library
and some don't for a reason I can not find.

In addition I found out later that the only wrapper script which is not
referencing the beast.jar archive is beauti which is refering to
beauti.jar.  However, this is IMHO totally useless and inconsequent
because beauti.jar contains a complete subset of all the classes in
beast.jar and I see no reason why we should carry this copy of code
for no obvios reason (except that if I try to rewrite the wrapper for
beauti I run in the same problem as for treeannotator and treestat
script which are not finding jam).

A thinkable alternative would be to change the build system in a way
that all wrappers would be use different jars and these in turn should
use one common jar as library.  While for my feeling this would be the
technically cleanest solution I doubt that upstream is really happy
about this change and without upstream support for the next versions
such an effort seems to be not very reasonable.

Any help is welcome

     Andreas.


On Fri, Feb 18, 2011 at 05:18:08PM +0100, Andreas Tille wrote:
> On Fri, Feb 18, 2011 at 04:37:53PM +0100, Vincent Fourmond wrote:
> > 
> >   This could mean that the version of jam in NEW was built without
> > support for one of its components (this can happen sometimes with
> > complex ant files), or that these components were split somehow. Where
> > can I get the package containing the jam.jar file ?
> 
> In NEW queue or for your comfort in
> 
>    http://people.debian.org/~tille/packages/figtree-help-wanted/
>  
> >   Ideally, you can just compare the output of zipinfo on both the
> > jam.jar file provided with the package and that found in the debian
> > package, and that will tell you what is missing...
> 
> $ zipinfo jam-0.0.r297.jar | grep jam/framework/SingleDocApplication
> -rw-r--r--  2.0 unx      615 b- defN 11-Feb-14 11:09 jam/framework/SingleDocApplication$1.class
> -rw-r--r--  2.0 unx     2266 b- defN 11-Feb-14 11:09 jam/framework/SingleDocApplication.class
> 
> It seems to be there - but hopefully you have some better clue than me
> to finally iron out this. 
> 
> Kind regards
> 
>        Andreas.
> 
> -- 
> http://fam-tille.de

-- 
http://fam-tille.de


Reply to: