Re: [gentoo-systemd] systemd-209+ and compat-libs

[Alex Xu]

On 25/02/14 04:58 PM, Michał Górny wrote:
> Hello, folks.
>
> First of all, two technical matters:
>
> 1. I think we have new people on systemd@g.o, you may want to subscribe
>    to gentoo-systemd@ mailing list if you didn't,
>
> 2. Does anyone feel like needing a team meeting?
>
> Now, for the core issue.
>
> As most of you probably already know, systemd-209 has replaced
> the separate libsystemd-* libraries with a single libsystemd.so.
> Upstream has provided --enable-compat-libs switch to install
> backwards-compat pkg-config files (that all use '-lsystemd')
> and backwards-compat .so libraries. The latter used some magic in -209
> and is just verbatim copy of libsystemd.so in -210.
>
> As I see it, we have three options now:
>
> 1. install both compat pkg-config files and libs (wasting space),
>
> 2. install only pkg-config files (a bit of build system hackery but
> easy),
>
> 3. do not install compat-libs and fix the rev-deps.
>
> I've committed a p.masked systemd-210 using option 2 today but it's
> still open to discussion. I'm currently testing all the rev-deps.
>
> I think that (2) is best since it leaves most of the packages working
> (only the few that don't do pkg-config break) and links them properly
> to the future lib. That is, when we drop the compat completely people
> will only have build-time failures and no mis-linked packages.
>
> I've started reporting bugs about packages that fail with it. I'm
> already explaining maintainers what the sit is and how to be
> future-proof. See bug #502422 [1] for an example.
>
> I don't think there's a point disabling compat completely right now.
> I'd rather wait a while till upstreams note the change and start
> updating the packages themselves. We can then only fix the few
> remaining ones as appropriate.
>
> What are your thoughts?
>
> [1]:https://bugs.gentoo.org/show_bug.cgi?id=502422
>

Can't we install the libs as symlinks?