nosracd
commented
5 months ago Are the LCM maintainers here interested in helping out with that work? We could CC you on relevant topics, or if we have build errors we might ping for any help.
If you're willing to push on packages then that would be much appreciated! We'd be happy to support you in any build issues or errors you come across.
Myself and some other of my team members might have the opportunity to push the version 1.5.0 upgrade into Debian. (See tracking bug.) Or if you have a newer version ready soon, we could try one that instead. (We'll be trying to move quickly, to possibly solve this in time for Ubuntu 24.04 release this spring.)
There haven't been many changes since the last release so I don't anticipate there being another one in the near future; I think it makes sense to use 1.5.0 for packages.
jwnimmer-tri
j-rivero
The LCM library and command-line tools have been distributed by Debian since ~2016:
Likewise for Ubuntu:
Unfortunately the packaged version in both is still stuck on the pretty old 1.3.1, rather that something newer like 1.5.0.
Myself and some other of my team members might have the opportunity to push the version 1.5.0 upgrade into Debian. (See tracking bug.) Or if you have a newer version ready soon, we could try one that instead. (We'll be trying to move quickly, to possibly solve this in time for Ubuntu 24.04 release this spring.)
Are the LCM maintainers here interested in helping out with that work? We could CC you on relevant topics, or if we have build errors we might ping for any help.
Or, this is also an opportunity for you to weigh in if you're prefer to see the Debian packages withdrawn, e.g., if you'd rather that other release channels supplant it (vcpkg, meson, forges, whatever) so that the Debian package doesn't fall stale again.
I'd welcome any feedback / discussion.