We are aware of this. However most distros are still using V3. Such an incompatible change is going to be difficult to resolve effectively :(
We may consider migrating away from XML
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the reply! Do you see any chance just to support both versions? In Gentoo, we still have both versions. But as - me, the maintainer - I would like to get mxml-3 removed in future, as most project have now patches :-) Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the reply! Do you see any chance just to support both versions? In Gentoo, we still have both versions. But as - me, the maintainer - I would like to get mxml-3 removed in future, as most project have now patches :-) Thanks!
Just an update to let you know that this is now in progress, but it might take
a while.
As a matter of interest, the differences are so significant that debian is
proposing to support both versions but with slightly different IDs so that they
can co-exist.
To add some background information: we pick up the MXML library with the help of package-config. The legacy versions of MXML v1 .. v3 used to ship a file 'mxml.pc' while the new version ships a file 'mxml4.pc'.
The Yoshimi build attempts to use the v4 first, and then falls back to the legacy case. The appropriate code variant is then compiled in and the Yoshimi executable is linked against that version of MXML. In many distributions, both library variants can be installed at the same time, but only one "development package". Thus, by installing the right "development package" before building Yoshimi, you can control which version of MXML will be used.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We are aware of this. However most distros are still using V3. Such an incompatible change is going to be difficult to resolve effectively :(
We may consider migrating away from XML
Thanks for the reply! Do you see any chance just to support both versions? In Gentoo, we still have both versions. But as - me, the maintainer - I would like to get mxml-3 removed in future, as most project have now patches :-) Thanks!
On Wed, 22 Jan 2025 17:59:31 -0000
"ConiKost" conikost@users.sourceforge.net wrote:
We are currently looking at the possibility of supporting both versions - our
users seem to run on quite a wide range of distro versions.
--
Will J Godfrey.
Related
Bugs: #39
Thanks! That sounds promising. Hope you find a way to support both :-)
On Thu, 23 Jan 2025 23:30:03 -0000
"ConiKost" conikost@users.sourceforge.net wrote:
Just an update to let you know that this is now in progress, but it might take
a while.
As a matter of interest, the differences are so significant that debian is
proposing to support both versions but with slightly different IDs so that they
can co-exist.
--
Will J Godfrey
Related
Bugs: #39
Thanks for the update! In Gentoo, we have the same approch and currently mxml is slotted, so v3 and v4 can be both installed at the same time.
I'm pleased to say this has now been done in Yoshimi V2,3.5.3, so in a weeks or so I'll close this bug.
To add some background information: we pick up the MXML library with the help of
package-config. The legacy versions of MXML v1 .. v3 used to ship a file 'mxml.pc' while the new version ships a file 'mxml4.pc'.The Yoshimi build attempts to use the v4 first, and then falls back to the legacy case. The appropriate code variant is then compiled in and the Yoshimi executable is linked against that version of MXML. In many distributions, both library variants can be installed at the same time, but only one "development package". Thus, by installing the right "development package" before building Yoshimi, you can control which version of MXML will be used.