The math/scilab port depends on the saxon.jar file from saxon-6.5.5 (textproc/saxon) in order to build its documentation. The scilab port is the only remaining port in the tree that depends on this old version of saxon. In particular, apache-openoffice-3.4.0_2 has been converted to depend on saxon-devel-9.1.0.7,1 (textproc/saxon-devel), which conflicts with saxon-6.5.5. That means that it is no longer possible to install both math/scilab and editors/openoffice-3 on the same host. Fix: The following patch removes the scilab dependency of on the textproc/saxon port by unpacking the saxon.jar file from the saxon-6.5.5 distfile into the saxon thirdparty build directory.
Responsible Changed From-To: freebsd-ports-bugs->truckman Submitter has GNATS access (via the GNATS Auto Assign Tool)
Maintainer of math/scilab, Please note that PR ports/168398 has just been submitted. If it contains a patch for an upgrade, an enhancement or a bug fix you agree on, reply to this email stating that you approve the patch and a committer will take care of it. The full text of the PR can be found at: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/168398 -- Edwin Groothuis via the GNATS Auto Assign Tool edwin@FreeBSD.org
State Changed From-To: open->feedback Awaiting maintainers feedback (via the GNATS Auto Assign Tool)
Approved -- Rob Farmer
truckman 2012-06-03 00:59:41 UTC FreeBSD ports repository (src committer) Modified files: math/scilab Makefile distinfo Log: Extract saxon.jar from the distfile for the textproc/saxon port into the thirdparty build directory for the scilab port. This allows the removal of the textproc/saxon build dependency from the scilab port so that scilab can be built on a host that has apache-openoffice-3.4.* installed. The latter port has a run dependency on textproc/saxon-devel, which conflicts with textproc/saxon. PR: 168398 Approved by: Rob Farmer <rfarmer AT predatorlabs.net> (maintainer) Revision Changes Path 1.89 +9 -4 ports/math/scilab/Makefile 1.23 +2 -0 ports/math/scilab/distinfo _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org"
State Changed From-To: feedback->closed Patch committed.
Hello guys;=0A=0AWhile reading about the commit I decided to do some=0Arese= arch:=0A=0AI think the conflict between saxon6 and saxon-devel=0A(actually = saxon-B) was resolved long ago when=0Asaxon-devel was updated.=0A=0ASaxon-d= evel now installs saxon9.jar and saxon9-*.jar=0Aso the package listing shou= ldn't conflict at all=0Awith Saxon-6.=0A=0AWhile here, I think the function= ality from Saxon-B is=0Aa superset of the functionality provided for saxon-= 6=0Aso if you can teach Scilab to use Saxon B, it would=0Agive us the best = of both worlds.=0A=0Abest regards,=0A=0APedro.=0A=0A(FWIW, I just submitted= an update to saxon-devel.)
On 3 Jun, Pedro F. Giffuni wrote: > Hello guys; > > While reading about the commit I decided to do some > research: > > I think the conflict between saxon6 and saxon-devel > (actually saxon-B) was resolved long ago when > saxon-devel was updated. > > Saxon-devel now installs saxon9.jar and saxon9-*.jar > so the package listing shouldn't conflict at all > with Saxon-6. Both ports install files with the same names under share/examples/saxon. I haven't compared the files to see if they are identical, but even if they are, removing one of the installed ports would remove files installed by the other. With this change to the math/scilab port, this should no longer be a problem because nothing else in ports requires Saxon-6. There is no longer any need to install textproc/saxon. > While here, I think the functionality from Saxon-B is > a superset of the functionality provided for saxon-6 > so if you can teach Scilab to use Saxon B, it would > give us the best of both worlds. I attempted to force Scilab to build using saxon9.jar and failed. Even if I bypassed the test that the configure script does to check the validity of the .jar file, the build failed later on. The Java API doesn't appear to match between the two versions of Saxon. The advice that I found about building on platforms that do not support saxon-6 is to drop saxon.jar into the thirdparty directory, where the configure script will find it. Nothing else from saxon-6 is required to build Scilab. It would be nice if Scilab could be built with a more recent version of Saxon, but that is probably something that needs to be done upstream.