- Added a new shell script to run Saxon from the command-line NOTE: The script is modified according to ${JAVAJARDIR} and ${PREFIX} prior to being installed. NOTE2: I am planning to port two other versions of Saxon. Saxon 7.9.1 is the -STABLE branch of the XSLT 2.0 flavor of Saxon and Saxon 8.0 is the -CURRENT branch. I think I will have the two ports named respectively textproc/saxon7 and textproc/saxon8. Together with this port, the three ports would CONFLICTS with each other as I believe it is not good to install different JAR files that implement different versions of the same classes in ${JAVAJARDIR}. Still I could be mistaken so please enlighten me on this one. The only other approach I can think of would be to repocopy this port to textproc/saxon6 and have the three as slave ports of textproc/saxon where you may use WITH[OUT]_XSLT2 and WITH[OUT]_EXPERIMENTAL to specify which version to install. Generated with FreeBSD Port Tools 0.50
Oops, I just realized I forgot to bump PORTREVISION...
Hum. I am working on improving textproc/xalan-j as well and I found out that it also uses this kind of sed magic to configure the shell script. However, this task is performed in a different target: do-configure. Now I realize that this is probably a better place for such a task. Do I need to re-submit a patch ? Herve
Responsible Changed From-To: freebsd-ports-bugs->glewis I'll take this.
Okay, I've digged through the documentation and website, and I think version 7.9.1 is not needed in the ports tree. So you want either version 6 (XSLT 1.0) or version 8 (XSLT 2.0 and XQuery 1.0). The only thing that the two ports would have in common would be the shell script so I don't know if we need to have 6 and 8 as slave ports actually. Life of user would be easy though, as he would be able to choose which features he wants to be installed through the use of OPTIONS in the metaport. So for now we could just make another port that conflicts with this one: textproc/saxon8. Herve
State Changed From-To: open->closed Committed, thanks!