A question on dynamic linking / version-changing libraries

[Brandon Allbery]

On Sun, Mar 5, 2017 at 11:43 AM, Michael <keybounce at gmail.com> wrote:

> Why does Macports generate libraries that follow the 1970-era linking
> strategy?


Because MacPorts is ports of programs for other platforms which don't have
frameworks... and do have politics (for example: Debian's strict adherence
to their package guidelines amounts to political interference that has
caused problems for users in the past several years, notably with regards
to availability of mate-desktop but there are other examples... like
google's monolithic software that you mentioned, where Google packages its
own software for Debian so they don't have to deal with the distribution
package politics). And we are not in a position to rewrite/reimplement
stuff into a frameworks-based model, if upstream hasn't already done it.

-- 
brandon s allbery kf8nh                               sine nomine associates
allbery.b at gmail.com                                  ballbery at sinenomine.net
unix, openafs, kerberos, infrastructure, xmonad        http://sinenomine.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20170305/92dbb31b/attachment.html>