[Pkg-octave-devel] Packaging Octave 3.8
sebastien at debian.org
Thu Jan 2 19:10:19 UTC 2014
Le lundi 30 décembre 2013 à 15:51 -0500, Mike Miller a écrit :
> One minor issue I've noticed with the new release is the way the JRE is
> dynamically linked in. With this configure option in debian/rules
> you might think it would use only that path for Java support, but in
> fact the following path is a built-in string in liboctinterp.so.2
> The result is that the binary package actually depends on the version of
> Java that was the default-jdk when it was built, and not what
> default-jre-headless is at run time. Fixing the build to only use the
> default-java path should help with maintainability and might avoid
> potential bugs.
> Adding the option
> to my configure command fixes that. This would of course need to be
> parameterized in some way to work on all ports, I'm not sure at the
> moment what that would look like. Perhaps this should also be reported
Thanks for noticing this. Clearly this is an issue that we should fix,
otherwise the package dependencies will not reflect the actual
dependencies if the default JDK were to change on a given arch. Do you
think you can propose a patch?
> Secondly, I've noticed that installed forge packages remain installed,
> but may not work with the updated octave packages. In particular,
> oct-files are no longer on the path. I don't know if this has been
> addressed previously, call for a binnmu on all forge packages?
Actually we will request a transition slot from the Release Team, as we
did for Octave 3.6. So the Release Team will schedule the necessary
binNMUs when they decide to proceed with the transition.
.''`. Sébastien Villemot
: :' : Debian Developer
`. `' http://www.dynare.org/sebastien
`- GPG Key: 4096R/381A7594
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 836 bytes
Desc: This is a digitally signed message part
More information about the Pkg-octave-devel