Hi Markus,
>1. usage of rpath
>
>(...)
>However the usage of rpath leads to problems during Debian package creation and is discouraged in Debian according to https://wiki.debian.org/RpathIssue
What exact problems are you experiencing during package creation?
Some skaware packages already exist for Debian, they do not turn off
rpath,
and they're working, as far as I can tell.
The issue with rpath raised by Debian is when there's a dependency
conflict in transitive dependencies. When this situation happens, it is
clearly a releng failure. Since skaware only depends on other
skaware packages and major releases are coordinated, this problem does
not happen; if it does, it's a bug and I will fix it ASAP.
I am reluctant to provide an option to disable rpath because in my
experience, disabling it can cause linking failure annoyances at every
step, whereas keeping it enable only causes problems when something is
already wrong either in a build or in versioning management of a
package.
If Debian can do without that option, and so far it looks like it has
been able to, I'd rather keep it that way.
>2. API breaking changes
>
>During 2.14.4.0 and 2.14.5.0, the removal of `skalibs_sigtable` caused an API breaking change in
>https://git.skarnet.org/cgi-bin/cgit.cgi/skalibs/commit/?id=32ac3aa6ac8f0dc9a240611a3696c0e5510b841d
That one, however, is on me: I failed to flag this commit as requiring
a major update. Sorry about that; it normally does not happen.
What is the simplest way for me to fix it? Should I cut a 2.15.0.0
release of skalibs ASAP, that you can then link all your new binaries
against, and usable versions will jump from 2.14.4.0 directly to
2.15.0.0?
--
Laurent
Received on Mon Mar 30 2026 - 00:22:02 CEST