2014/1/16 Lennart Poettering <lenn...@poettering.net>: > So I am pretty sure libsystemd-id128, libsystemd-login, > libsystemd-journal should just end up in a single libsystemd.so together > with the event loop, the bus, the asyncns stuff and more. All this > functinality requires each other, and should nto pull in its own copy of > src/shared/*.c each time. > > There are some exceptions to this though. For example, I am unsure about > libsystemd-daemon: it's relatively easy to maintain this in its own lib, > sicne so far it actually doesn't use any of the shared code, because > its' embeddable. But then agaiun, given that this library evolves too, > and given that distros generally don't like embedding anyway, we should > probably just merge it into libsystemd.so too, in particular since the > functions it provides are really low-level stuff. libsystemd-dhcp > however really sounds like something that will always be consumer of > services, never > provider of services from this new libsystemd.so, and the set of > programs making use of it will always be very small, so we can and > should certainly keep it a seperate lib. > > I hope this makes some sense...
Would that mean you intend to break existing software which uses those libraries, especially libsystemd-daemon. Do you intend to at least keep the .pc files so a recompilation would be sufficient? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
