> On 6 Mar 2017, at 09:53, Chris Jones wrote:
>
>
> Building statically is also a security nightmare.
>
> If I have a dynamic libFoo.so, that a lot of other libraries and applications
> dynamically link against, that is suddenly found to have a major security
> bug, then once libFoo.so is up
Building statically is also a security nightmare.
If I have a dynamic libFoo.so, that a lot of other libraries and
applications dynamically link against, that is suddenly found to have a
major security bug, then once libFoo.so is updated I know everything
else using it is also fixed. If inste
On Sun, Mar 5, 2017 at 1:47 PM, Michael wrote:
>
> On 2017-03-05, at 9:49 AM, Brandon Allbery wrote:
> > Also fixed-*path* libraries are part of the Mach-O format and the
> tooling does not exist to override this well...
>
> Is this why a program compiled against a brew installation of qt5 in
> /
Oh you can build stuff statically but that is a kind of manual work and not for
MP to do.
> On 5. Mar 2017, at 19:47, Michael wrote:
>
>
>> On 2017-03-05, at 9:49 AM, Brandon Allbery wrote:
>> Also fixed-*path* libraries are part of the Mach-O format and the tooling
>> does not exist to over
On 2017-03-05, at 9:49 AM, Brandon Allbery wrote:
> Also fixed-*path* libraries are part of the Mach-O format and the tooling
> does not exist to override this well...
Is this why a program compiled against a brew installation of qt5 in /usr/opt
won't work with a ports installation of qt5 in /
On Sun, Mar 5, 2017 at 12:33 PM, Michael wrote:
> I'm curious more as to: Why do we still generate code that links against a
> fixed-name library? Why does that name not include a version/API reference?
> Why not make static linked stuff, so that changes in the libraries don't
> break things?
M
On 2017-03-05, at 9:27 AM, Brandon Allbery wrote:
>
> On Sun, Mar 5, 2017 at 11:43 AM, Michael wrote:
> Why does Macports generate libraries that follow the 1970-era linking
> strategy?
>
> ... And we are not in a position to rewrite/reimplement stuff into a
> frameworks-based model, if ups
On Sun, Mar 5, 2017 at 11:43 AM, Michael 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 pack
