[systemd-devel] [systemd-commits] 4 commits - .gitignore Makefile.am man/sd_bus_creds_get_pid.xml man/sd_bus_creds_new_from_pid.xml man/sd_bus_error.xml man/sd_bus_label_escape.xml man/sd_bus_message_get_cookie.xml man/sd_bus_new.xml man/sd_bus_open_user.xml man/sd_bus_request_name.xml src/libsystemd src/libsystemd-bus src/libsystemd-dhcp src/libsystemd-rtnl src/systemd TODO

[Michael Biebl]

2014/1/16 Kay Sievers <kay at vrfy.org>:
> On Thu, Jan 16, 2014 at 7:00 PM, Michael Biebl <mbiebl at gmail.com> wrote:
>> 2014/1/16 Lennart Poettering <lennart at poettering.net>:
>
>>> Well, it can certainly continue to use and build against the old version
>>> for a while, no?
>>
>> We'd have to make pre-systemd-209 and systemd-209 packages
>> co-installable (different source package names etc.) to be able to
>> continue to provide the old version. That is not really fun.
>
> Why? The lib is packaged separately, isn't it? What does it have to do
> with the systemd package?

Packaged separately in the sense that the systemd source package
builds a libsystemd-daemon0 binary package (among others).
In systemd v209 we could no longer build such a libsystemd-daemon0
binary package from the systemd source package.
We'd have to introduce a separate source package (based on systemd pre
209) named differently then systemd if we want to be able to continue
to build libsystemd-daemon0.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?