On Aug 7, 2022, at 08:05, Steven Smith wrote:
> Someday, one hopes that there will be a cleanup of all the tcl code that
> breaks for prefix paths with spaces and non-ascii characters, but that’s
> aspirational, not reality.
Many ports use build systems like autoconf that do not support paths t
On 2022-8-7 23:05 , Steven Smith wrote:
You can use any prefix you want, precompiled binaries or no. Just go
ahead and do it.
Well, almost. There’s this caveat:
Options for MacPorts general operating characteristics.
prefix
Sets the directory where ports are installed. Any path may be u
On 2022-8-7 18:29 , Jordan Ellis Coppard via macports-dev wrote:
Hello,
I read in the docs that if MacPorts is installed anywhere other than
/opt/local that precompiled binaries can not be used. I cannot find this
statement again so I am unsure if there was additional explanation for
why; so
> You can use any prefix you want, precompiled binaries or no. Just go ahead
> and do it.
Well, almost. There’s this caveat:
> Options for MacPorts general operating characteristics.
>
> prefix
> Sets the directory where ports are installed. Any path may be used but those
> with spaces and/or
You can use any prefix you want, precompiled binaries or no. Just go ahead and
do it.
It appears that you may be misinterpreting the docs. This page simply tells
devs not to do stuff with installers that will conflict with existing files in
/opt/local: https://guide.macports.org/#using.binaries
Hello,
I read in the docs that if MacPorts is installed anywhere other than
/opt/local that precompiled binaries can not be used. I cannot find this
statement again so I am unsure if there was additional explanation for
why; so.. why?
I'd like to be able to use MacPorts at a custom prefix b
