El 22/02/15 a las 22:37, Luke Kenneth Casson Leighton escribió:
well, you could provide hints in the documentation (and force them to
be read by deliberately changing the API)
Wow.. so what you want is even nuttier than I thought..
that would be a good place to start, showing people how to begin the
process of dlopen()ing libsystemd0, documenting it well so that it was
easy to follow.
No, again. using dlopen with libsystemd is crazy, you will only turn
software even more complex and ugly than already is. and with this
little gem:
-- a/Makefile.am
+++ b/Makefile.am
@@ -3046,7 +3046,7 @@ libsystemd_la_CFLAGS = \
$(libsystemd_journal_internal_la_CFLAGS)
libsystemd_la_LDFLAGS = \
- $(AM_LDFLAGS) \
+ $(AM_LDFLAGS) -Wl,-z,nodlopen \
we can stop the madness from becoming reality :-)
* distros are forced to follow suit on upstream decisions, without
consulting what any other distros do
No, distros are welcome to come here and influence the direction of the
project and its components, before reality imposes itself. those who do
the work, make decisions.
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
