log4shib and pkg-config

[Ferenc Wágner]

"Cantor, Scott" <cantor.2 at osu.edu> writes:

>> Sure, I'll do so.  No need to hurry this, I just wanted to know your
>> attitude towards the matter before investing considerable work into it.
>> Knowing you're willing to follow I'll just go ahead and gather some
>> experience for the next release cycle.
>
> I really don't have the time anymore to track autoconf developments,
> so if there are things we need to do to modernize, I'm fine with it.

Hi Scott,

I published my current patch queue for xmltooling at
https://anonscm.debian.org/cgit/pkg-shibboleth/xmltooling.git/log/?h=patch-queue/debian/experimental
(an ephemeral branch just providing a preview).

The interesting part is the tip of the branch, debian/experimental..
Only commit "Remove .pl extension of cxxtestgen" is Debian-specific.
The rest gets the build system use pkg-config info for finding the
dependencies, provide pkg-config info for the users of the xmltooling
libraries, and integrates the test suite into the build (unrelated).
I also made linking more granular, stopping overlinking.

I tried to use mainstream solutions and hope that any problems arising
on your supported platforms (for example PKG_INSTALLDIR macro being
unavailable in pkg-config older than 0.27) will be easily fixable.  Up
to now I tested the full Shibboleth stack on Debian unstable, with
similar patches applied to the other packages.  The above xmltooling
changes already depend on the last three xml-security-c modifications at
https://anonscm.debian.org/cgit/pkg-shibboleth/xml-security-c.git/log/?h=patch-queue/master
I killed backwards compatibility in this test run, but that mainly
matters for xml-security-c, because xmltooling, opensaml2 and
shibboleth-sp2 are often released in lockstep and log4shib already
provides a usable pkg-config file.  A distribution can make a
coordinated transition, but you as upstream are in a different position.
How do you think this could work out?
-- 
Thanks,
Feri