Upcoming Shibboleth-related package transition

Scott Cantor cantor.2 at osu.edu
Tue Jul 21 21:58:55 UTC 2009


Russ Allbery wrote on 2009-07-21:
> Oh, that part.  The general rule is that you should bump the second number
> when you add new interfaces and the third when you make any code changes
> (on Linux; this varies by platform), but so far as I know, they're not
> actually used by software and therefore it doesn't matter.

Well, it's used on most platforms I know of because it lets you co-install
libs that vary in the second number but makes sure you have a single copy
that vary in the third.

My issue is whether I'm breaking some package manager (specifically yours)
by updating the source version (because the automake files changed) but not
the lib version (including the revision). So you'd have two source tarballs
that generate the exact same libtool version.

With RPM, this is not an issue. I'm just asking if it's a problem for
Debian.

If it's a problem, I either have to maintain a private copy of the source
for now when I generate RPMs, or bump the libtool version just "because".

-- Scott





More information about the Pkg-shibboleth-devel mailing list