gfxutil @1.83b: wrong worksrcdir

[ryandesign (Ryan Carsten Schmidt)]

​https://build.macports.org/builders/ports-13_arm64-builder/builds/9373/steps/install-port/logs/stdio

sh: line 0: cd: /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_sysutils_gfxutil/gfxutil/work/gfxutil-1.83b: No such file or directory

worksrcdir is wrong. There is no directory gfxutil-1.83b; it's called acidanthera-gfxutil-2f6f1b1.

[i0ntempest]

I have seen this before once, I think it's caused by a recent change in MacPorts base iirc? How do I go with fixing this, just overwrite worksrcdir variable?

[jmroot (Joshua Root)]

Yes, either set worksrcdir to the actual name of the extracted source directory where you want the build commands to be run, or rename the directory in post-extract to match the default worksrcdir value. The GitHub portgroup attempts to rename the directory for you since they often have hashes in their names, but it can only do that if there is one directory in the workpath.

[ryandesign (Ryan Carsten Schmidt)]

Replying to jmroot:

The GitHub portgroup attempts to rename the directory for you since they often have hashes in their names, but it can only do that if there is one directory in the workpath.

Yes, that's the situation now, with MacPorts 2.8.1. MacPorts 2.8.0 was able to build this port as is.

[ryandesign (Ryan Carsten Schmidt)]

You disabled and then removed the code in the github portgroup that handled this situation.

[jmroot (Joshua Root)]

Feel free to bring it back if it still does something useful. The gitlab portgroup had very similar code commented out with comments indicating that it was no longer needed (due to the previous symlinking behaviour in base), and I didn't get any feedback on the changes at the time.

[i0ntempest]

In 90e301e8c3fdec53e08ee69897af425792553486/macports-ports (master):

gfxutil: manually handle worksrcdir renaming

Closes: #67058