https://bugzilla.novell.com/show_bug.cgi?id=780666
https://bugzilla.novell.com/show_bug.cgi?id=780666#c3
Thomas Schraitle
Well, don't you want to keep the maintenance of saxon at all? I personally dislike such xslt, docbook thingie, so cannot even test my changes.
Well, you may dislike these things, but others use them in their daily work (me and my team included). ;) If you need someone to test, count me as a volunteer. :)
Anyway - the downgrade of saxon is not possible - the best I can do it add saxon6 with 6.5.5 into Factory (would be that enough?)
Well, this is/was an error as they are different things: version 6.x supports XSLT 1.0, and version 9.x is for XSLT 2.0. I'm sorry if that's troublesome for you, but that's just the way it is. :) Ok, but anyway. If you can't revert this change to the way it was in openSUSE 12.1, the question is now, how we deal it in the future? The following options come to my mind: 1. Use saxon6 as package name and /usr/bin/saxon6 as script name 2. Use saxon6 as package name and /usr/bin/saxon as script name (conflicts with saxon9, probably. ) 3. Use saxon6 as package name and use /usr/bin/saxon as link which is created by the "alternatives" method (similar to the java command/link). 4. Others...? I'm not sure which one is the best, but I have a slight preference for option 2. That means, the "saxon" name isn't "owned" by anyone, but created on demand (as with the "java" command). All other versions (previous and future) contains the explicit major number in its script name, like saxon6, saxon9, saxon10... Drawback is, that someone can be surprised if someone changes from version 6 to version 9. What do you think? Would that be feasible? Thanks! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.