- symbols. So far, we managed to workaround that by linking a
- copy of a good part of our code into each of these libraries
- again and again, which however makes certain things hard to
- do, like sharing static variables. Also, it substantially
- increases footprint. With this change, there is only one
- library for the basic APIs systemd provides. Also,
- "sd-bus.h", "sd-memfd.h", "sd-event.h", "sd-rtnl.h",
- "sd-resolve.h", "sd-utf8.h" are found in this library as
- well, however are subject to the --enable-kdbus switch (see
- below). Note that "sd-dhcp.h" and "sd-daemon.h" are not part
- of this libraries (the former because it only consumes,
- never provides services of/to other APIs, and the latter
- because it is completely standalone). To make the transition
- from the separate libraries to the unified one easy, we
+ symbols. So far, we've managed to workaround that by linking
+ a copy of a good part of our code into each of these
+ libraries again and again, which, however, makes certain
+ things hard to do, like sharing static variables. Also, it
+ substantially increases footprint. With this change, there
+ is only one library for the basic APIs systemd
+ provides. Also, "sd-bus.h", "sd-memfd.h", "sd-event.h",
+ "sd-rtnl.h", "sd-resolve.h", "sd-utf8.h" are found in this
+ library as well, however are subject to the --enable-kdbus
+ switch (see below). Note that "sd-dhcp-client.h" is not part
+ of this library (this is because it only consumes, never
+ provides, services of/to other APIs). To make the transition
+ easy from the separate libraries to the unified one, we