David Pirotte <[email protected]> writes: >> ... >> For new projects likely. Is there a simple update-path for projects >> currently using g-wrap? > > The simple update path is to drop any g-wrap generated bindings, then > read the nyacc ffi-helper doc, which comes with examples as well, then > write a simple module to be compiled as recommended by nyacc ffo-helper > (not gona repeat this here), then use those bindings and/or provide a > higher level api ...
This is not a simple update path but a re-implementation. Which sounds like there is no simple update path. Regarding the other email: >>... especially because g-wrap is marked as Production/Stable on >> savannah > > That is probably because their maintainer did not think (or bother) to > properly tag the savannah project repo. Doesn’t change that it is tagged as stable, so throwing it out breaks a promise to existing users. Debian popcon shows that g-wrap is still a lot more widespread than nyacc: https://qa.debian.org/popcon-graph.php?packages=guile-g-wrap+nyacc&show_installed=on&want_legend=on&want_ticks=on&from_date=&to_date=&hlght_date=&date_fmt=%25Y&beenhere=1 Are there package install statistics from other distributions? And download statistics from the savannah project? > All-in-all, no distro should propose g-wrap anymore, that was the > meaning of my answer to Greg. Providing g-wrap does not mean proposing it. It just means that tools that already use it continue to work. And apart from not seeing a new release, there has been no notification that it’s deprecated. So I think if it can be made compatible with Guile 3 without too much work, it should be. And the website-, savannah project-, and package-descriptions updated to note that g-wrap has seen no active development for a decade, so new projects should use the nyacc ffi-helper instead. Best wishes, Arne -- Unpolitisch sein heißt politisch sein, ohne es zu merken. https://www.draketo.de
signature.asc
Description: PGP signature
