Re: Co-existance of MacPorts and Brew?
Hi, On Wed, Feb 15, 2023 at 02:54:40PM -0500, André-John Mas wrote: > What is the current status of co-existence of Brew and MacPorts on the > same machine? Previously this was meant to be a problem. It's less of a problem these days on Apple Silicon, because Homebrew moved away from /usr/local, which was in the default search path for compilers. However, many software packages automatically look for software in Homebrew locations, and that can and will still cause issues in MacPorts. We used to have trace mode as a tool to mitigate most of these issues, but Apple's most recent security measures broke this again, so it currently doesn't work on Ventura, or any Apple Silicon machines: https://trac.macports.org/ticket/66358 > The latest one I ran into was Vagrant, which indicates how to use Brew > to install, but nothing for MacPorts: > > https://developer.hashicorp.com/vagrant/downloads That's because brew doesn't build Vagrant from source but installs hashicorp's prebuilt binary [1]. This isn't MacPorts' policy, as we always want to build software we ship from source on our build machines. Installing vagrant from brew is no different from installing their dmg directly. > Also, there doesn't seem to a version of Vagrant in MacPorts. Vagrant is actively hostile to others building and packaging their software. You *can* build it yourself, and it's not very complicated either, since it just uses ruby bundler, but any copy you build yourself will print this warning *on* *every* *single* *command* *you* *run*, sometimes even breaking usability in the process, such as when running vagrant ssh-config, which will clobber stdout with this warning: | You appear to be running Vagrant outside of the official installers. | Note that the installers are what ensure that Vagrant has all required | dependencies, and Vagrant assumes that these dependencies exist. By | running outside of the installer environment, Vagrant may not function | properly. To remove this warning, install Vagrant using one of the | official packages from vagrantup.com. I know it's sometimes a useful tool, but let me tell you, if I didn't have to use it for what I'm currently doing, I'd actively avoid it like the plague for this behavior that's IMO open source in writing only, not in spirit. [1]: https://github.com/hashicorp/homebrew-tap/blob/master/Casks/hashicorp-vagrant.rb -- Clemens
Re: Co-existance of MacPorts and Brew?
Yeah, and while there are a lot of brew instructions, they're sad - cuz they don't tell you that they only work with the two most recent versions of MacOS. If you're like me, running Mojave, or anything older than current - 1, you're out of look. Thankfully, macports just keeps ticking (I ditched homebrew after asking the maintainer if he'd consider supporting Mojave and he said, no plans to do so). That was quite a while ago :). I upgraded full on macports a couple of days ago no problems and am grateful for macports! On 2/15/23 3:04 PM, chilli.names...@gmail.com wrote: Whenever I find something not on MacPorts, I always request it from the developer, who is usually accommodating. On Feb 15, 2023, at 14:55, André-John Mas wrote: Hiya, What is the current status of co-existence of Brew and MacPorts on the same machine? Previously this was meant to be a problem. I am asking this question, since I am finding more and more recipes pointing towards using Brew, instead of MacPorts. The latest one I ran into was Vagrant, which indicates how to use Brew to install, but nothing for MacPorts: https://developer.hashicorp.com/vagrant/downloads Also, there doesn't seem to a version of Vagrant in MacPorts. Andre
Re: Co-existance of MacPorts and Brew?
On 2023-02-15 at 14:54:40 UTC-0500 (Wed, 15 Feb 2023 14:54:40 -0500) André-John Mas is rumored to have said: Hiya, What is the current status of co-existence of Brew and MacPorts on the same machine? Previously this was meant to be a problem. It remains problematic. The conflict is intrinsic, and cannot be solved completely without one of the projects adopting the policies and practices of the other in a fundamentally incompatible way. With that baseline understanding, you can use both never (if you are careful and lucky,) have a problem. I am asking this question, since I am finding more and more recipes pointing towards using Brew, instead of MacPorts. If you try to use both it will *mostly* work and you may never encounter a problem, but if you do run into a conflict, it could be very hard to find a solution. The underlying problem is that many open source packages have /usr/local hardcoded into their build, install, or load, such that even if they are made to live in and use the world under /opt/local (i.e. MacPorts) they may still look for shared libraries under /usr/local first. If you have a Brew world under /usr/local, there's a significant chance that if you build MacPorts packages from source, some configure script will pick stuff in /usr/local/ to use instead of the /opt/local components. That may work, until the next upgrade of the relevant packages on one side or the other. The latest one I ran into was Vagrant, which indicates how to use Brew to install, but nothing for MacPorts: https://developer.hashicorp.com/vagrant/downloads Also, there doesn't seem to a version of Vagrant in MacPorts. If there's a recipe for brew, it shouldn't be terribly hard to create a port for MacPorts. All it takes is someone willing and able to do the work of creating the portfile and porting patches as needed. -- Bill Cole b...@scconsult.com or billc...@apache.org (AKA @grumpybozo and many *@billmail.scconsult.com addresses) Not Currently Available For Hire
Re: Co-existance of MacPorts and Brew?
Whenever I find something not on MacPorts, I always request it from the developer, who is usually accommodating. > On Feb 15, 2023, at 14:55, André-John Mas wrote: > > Hiya, > > What is the current status of co-existence of Brew and MacPorts on the same > machine? > Previously this was meant to be a problem. > > I am asking this question, since I am finding more and more recipes pointing > towards > using Brew, instead of MacPorts. > > The latest one I ran into was Vagrant, which indicates how to use Brew to > install, but > nothing for MacPorts: > > https://developer.hashicorp.com/vagrant/downloads > > Also, there doesn't seem to a version of Vagrant in MacPorts. > > Andre
Co-existance of MacPorts and Brew?
Hiya, What is the current status of co-existence of Brew and MacPorts on the same machine? Previously this was meant to be a problem. I am asking this question, since I am finding more and more recipes pointing towards using Brew, instead of MacPorts. The latest one I ran into was Vagrant, which indicates how to use Brew to install, but nothing for MacPorts: https://developer.hashicorp.com/vagrant/downloads Also, there doesn't seem to a version of Vagrant in MacPorts. Andre
