On Wed, Jun 24, 2015 at 6:10 PM, Christopher Ramos < [email protected]> wrote:
> Hm, well I understand your point and, while valid, it's not relevant to my > point. For one, I'm not referring to the problem with a user downloading > malicious code or code that does something the user doesn't understand. > Macports, like the Mac App Store, is *curated*; it's not the same thing as > going to some fly-by-night website, downloading, and installing willy nilly. > > A better analogy would be Mozilla hosting a FF add-on that, by proxy, > interferes with the functionality of other add-ons. > So your argument is that Apple should have warnings plastered over their Xcode download that it would enable you to break their system by building conflicting software? (Which is absolutely true.) In any case, MacPorts is not the Mac App Store, and it was created in large part specifically to *enable* building software by providing development tools that Apple does not, including recent versions of git etc. Likewise for HomeBrew. Built-in nannies are not desired, nor welcome; we're trying to *get away* from Apple's nannies. -- brandon s allbery kf8nh sine nomine associates [email protected] [email protected] unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
_______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
