search

gyoto / Gyoto

General relativitY Orbit Tracer of the Observatoire de Paris
http://gyoto.obspm.fr/
GNU General Public License v3.0
43 stars 25 forks source link

Gyoto requires xerces-c #25

Open paumard opened 1 week ago

paumard commented 1 week ago

We have received indication from the xerces-c maintainers that its usage should be deprecated. As Gyoto rather strongly relies on XML i/o, a longer term alternative should be sought for.

scantor commented 1 week ago

I wasn't intending to turn the macport issue into a larger conversation for all sorts of projects, but if it's news to people, I'm happy to see the attention.

Xerces has had basically one maintainer for a decade or more that is only doing so to support his own project (that's me), and is actively working to get off of it, and within a few years, I will cut off all involvement.

Xerces needs maintainers, desperately. It is dead in all but name and has been for a long while. Otherwise, yeah, I'd urge you find alternatives, but I know very well how non-trivial it is to get off it or I would have done so many years back!

paumard commented 1 week ago

Thanks for the information, xerces-c has been working like a charm for us over all these years!

Cheers

Le 14/11/2024 à 18:15, Scott Cantor a écrit :

I wasn't intending to turn the macport issue into a larger conversation for all sorts of projects, but if it's news to people, I'm happy to see the attention.

Xerces has had basically one maintainer for a decade or more that is only doing so to support his own project (that's me), and is actively working to get off of it, and within a few years, I will cut off all involvement.

Xerces needs maintainers, desperately. It is dead in all but name and has been for a long while. Otherwise, yeah, I'd urge you find alternatives, but I know very well how non-trivial it is to get off it or I would have done so many years back!

— Reply to this email directly, view it on GitHub <https://github.com/ gyoto/Gyoto/issues/25#issuecomment-2476988174>, or unsubscribe <https:// github.com/notifications/unsubscribe-auth/ AAEXSGWIPJP6LEQBZSKLMWL2ATLDDAVCNFSM6AAAAABRZMCTQWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZWHE4DQMJXGQ>. You are receiving this because you authored the thread.Message ID: @.***>

--

scantor commented 1 week ago

You can follow the latest conversations yourself [1] but suffice to say, there is a difference of opinion over how safe it is to stay with it long term, and you would need to judge for yourself.

It's an old, ongoing argument, and because of it, there are no official statements about what the state of the project or is or any clear sign of the potential risk.

As I say in the issue, there's probably a gray area between "deprecated" and "at risk" but YMMV.

(And certainly if you care and need the code, becoming contributors is a really good way to demonstrate that.)

[1] https://issues.apache.org/jira/browse/XERCESC-2257