On 01/10/2017 12:06 AM, langdon wrote:
Now, there are some use cases where the interop of the components is
very important and a distribution enables this because all the things
are tightly integrated. However, there is no particularly good reason
for httpd and kde to be tightly integrated. Why can't they be using
different versions of libraries assuming they are equally secure but
different in feature set?
Apache httpd and KDE are very interesting examples. Both KDE and Apache
httpd integrate with Subversion, on two levels: KDE has Subversion
client support, Apache httpd has server support. And Subversion is
implemented using apr (the Apache Portable Runtime library).
So unless we start building Subversion twice, once for use with Apache
httpd, and once for use within KDE, modules containing KDE and Apache
httpd will have to agree on the same version of Subversion and the same
version of apr. To cut down support overhead, we'd probably want them
to use the same versions, too, but this might not always be possible
(e.g., newer upstream versions may have obliterate support, which would
be considered an important server-side feature, but also change the
working copy format, which would not be acceptable for a stable desktop
release).
Thanks,
Florian