Hi Mojca, How do you hide a prefix when installing?
David On Tue, Aug 29, 2017 at 2:39 PM, Mojca Miklavec < [email protected]> wrote: > On 29 August 2017 at 23:24, Ryan Schmidt wrote: > > On Aug 29, 2017, at 07:08, db wrote: > > > >> best practice for running macports along with homebrew > > > > The best practice is not to do that. We don't support it. It can cause > you problems that we don't want to spend time investigating, because they > wouldn't be problems if you hadn't also used a second package manager. > > ... but if you really really want to have Homebrow installed alongside > MacPorts, then the most important piece of advice is NOT to install > Homebrew to its default location. Put it under some obscure prefix and > ideally hide the path to Homebrew while installing new ports with > MacPorts. > > Having Hombrew under /usr/local and then using MacPorts (esp. without > the trace mode) is the best recipe for running into numerous problems > that are nearly impossible to fix. I would say that it's generally a > relatively bad idea to have Homebrew inside /usr/local, but of course > that depends on usage patterns. > > Similarly, when you install Homebrew packages, hide the prefix to > MacPorts (even though some badly written configure scripts may still > look for files inside MacPorts prefix, but that's not as frequent). > > As a general rule of thumb having just one manager is a lot > better/easier/safer. With two systems it's easy to run into problems > unless you know very well what you are doing. > > But most important: in case you do end up with two systems, make sure > to quadruple check before submitting any bug reports to make sure that > the error is not due to the packages intermixed with each other. And > make sure to mention the fact that you are using two package managers > in any tickets or emails. > > Mojca >
