MacPorts 2.11.0: oddly named workdirs
Joshua Root
jmr at macports.org
Mon Jul 14 09:43:37 UTC 2025
On 14/7/2025 19:22, Chris Jones via macports-dev wrote:
> Hi,
>
> On 14/07/2025 9:32 am, Sergey Fedorov wrote:
>> It is not a bug, but a feature? Workdirs are no longer named after
>> ports, but start with a few letters of a ports name, followed by
>> random characters.
Yes. <https://trac.macports.org/ticket/70539>
> Yeah, I've noticed this and I have found it interferes with the use of
> ccache when building ports. I have enabled this for all my port builds,
> as I am often working on large ports (LLVM) and it *really* helps with
> rebuilds. However, this new feature seems to result in the build dir
> being different each rebuild, due to the random characters, and this of
> course renders the ccache invalid and useless.
Are we not setting CCACHE_BASEDIR?
> How is this random string created, and why does it change whenever I
> make small portfile changes ?
<https://github.com/macports/macports-base/blob/v2.11.1/src/port1.0/portutil.tcl#L1732>
> Is there a way to disable this random string and go back to something
> similar to before, particularly when the use of ccache is enabled ?
The traditional work path still exists as a symlink to the shortened one.
- Josh
More information about the macports-dev
mailing list