Supporting installing arbitrary port versions
Steven Smith
steve.t.smith at gmail.com
Sun Oct 4 14:13:17 UTC 2020
This is a Terrible Idea.
The first rule of computer security is to update your stuff.
Adding the complexity of allowing arbitrary software versions means that now we have to make sure that we update our stuff and make sure that we’re not still running old, insecure code even after we’ve updated. It’s asking for trouble.
I don’t want Apple to give me the option of running old ssh (or any other old code) when I update macOS, and I don’t want MacPorts to give me the same option.
And that’s on top of the unworkable maintenance issues discussed before.
A big Nope, both as a user and a port maintainer.
> On Oct 3, 2020, at 11:00 AM, Ryan Schmidt <ryandesign at macports.org> wrote:
>
> It would be a major project if it were clear how it could possibly work and it were just a matter of doing it. But so far I have no idea how it could work.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20201004/40e2197d/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3898 bytes
Desc: not available
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20201004/40e2197d/attachment.bin>
More information about the macports-dev
mailing list