Ran across this issue (not touched by anyone in over a decade!), and as I've 
caught a bit of a packaging bug lately I'm tempted to try to take it on (and 
likely fail where others before me have but we'll see).

I have a bit of an axe to grind against academic code that lacks good build 
systems or packaging, and enjoy overcoming such hurdles (this developed while 
working on SageMath and helping to improve its packaging some years ago :)

Also had recent successes is helping improve AST's build system.

Speaking of AST since it was mentioned here as a dependent of LevMar, that is 
no longer the case.  In fact shortly after the last update on this bug (but 
still over a decade ago), AST dropped it in favor of CMINPACK: 
https://github.com/Starlink/ast/commit/3e5b6ad49636e6a9cbd37a5e7704c3c925375372

So that is one less hurdle.  I can't say for sure about the other packages that 
use it.

One question I would have is, if ever there is a useable "liblevmar" packaged 
as a shared library in Debian, would the downstream dependents have to be 
simultaneously updated to *use* it, or can the by updated on a case-by-case 
basis where it's even possible?

Best,
Madison

Reply via email to