LS,
One of the packages in Debian is libzeep, I contributed that library
since I needed it at the time for the other programs I wanted to
contribute to Debian. But, to reduce the complexity of building my
software outside Debian I removed most of the dependencies on libzeep.
What remains is behind a switch that is turned off for Debian (e.g. the
web server part of dssp).
This library in itself is one of the most important parts of the
software I write in my day job. It can be used to build fast and
responsive web applications in C++. It is in production in many
applications that are used on a large scale, examples are
https://pdb-redo.eu/ and https://alphafill.eu . But none of these
applications will ever be in Debian. Mostly because they are simply not
useful in the context of Debian, but also because it will be too much
work to make Debian packages out of them, mainly because they need NPM
packages and I don't see how that could be packaged easily.
Now, I updated libzeep some time ago and prepared a package for Debian
that ended up in NEW. But this took so long that by now the upstream
libzeep is a major release further, the one in experimental is out of
date already. To make things worse, I split the library in two, one for
web related stuff and another that is a feature rich C++ xml library
(mxml, see: https://forge.hekkelman.net/maarten/mxml ).
So, the question is, is it worth the trouble to update libzeep in Debian
which would require the upload of two new libraries (zeep and mxml). Or,
since no packages are depending on libzeep, should we simply remove
libzeep altogether?
I'm perfectly willing to do some work like creating the debian packages.
But if no one is using this, it might not be worth it.
Any thoughts?
-maarten
- libzeep Maarten L. Hekkelman
-
