Tom Schraitle

**Commented by *anonymous on 2012-11-08 10:32** Additional note: naming change from openSUSE 12.1 to 12.2: version 6.5 of Saxon will be in package "saxon6" with the script "saxon6". Packages for...

**Updated by fsundermeyer on 2012-11-30 20:20** - **summary**: Support Saxon version 6 and 9 --> Support Saxon version 9 - **assigned_to**: Thomas Schraitle --> Frank Sundermeyer - **info_provider**: Frank Sundermeyer...

**Commented by fsundermeyer on 2012-11-30 20:20** saxon6 is now fully supported (SVN commit 2309). saxon9 support is not required until we have XSLT 2.0 stylesheets, therefore adjusting Ticket title and...

I think, for DAPS this issue can be closed. For the SUSE stylesheets parts, this is covered in issue opensuse/suse-xsl#505

> Thanks for putting this together. You're welcome. :slightly_smiling_face: Thanks for considering my idea. > The `init` can be an opinionated command. > If I understand it right, the purpose...

Funny coincidence, I've played around with these extended matching parts in PR #367. :smile: It may or may not be integrated into the main branch, depending on the outcome of...

Would something like this be useful? ```python def iscompatible(v1: Version, v2: Version): if v1.major != v2.major: return False if v1.minor < v2.minor: return False if v1.prerelease != v2.prerelease: return False...

Both `is_compatible` and `is_breaking` are possible. I have three questions: 1. Should we make `is_compatible` an alias of `is_breaking`? Or would it be confusing? Probably there should be only one...

> 1. [...] > An alias would be very confusing, since is 'breaking' is opposite of 'compatible'. ;) Possibly yes. :slightly_smiling_face: My brain didn't catch that in the early morning....

It seems to me, the `is_compatible` is basically an extended comparison like the tilde comparison: ~1.2.3 := >=1.2.3 and