configure script does not expand "~" for applications_dir and frameworks_dir

[von.helmut@…]

./configure --prefix=~/path/to/macports installs to $HOME. This is reflected in the macports.conf file on the prefix line as /Users/name/path/to/macports. But on other _dir lines in the .conf file, the ~ is not expanded (in my case i specified --with-applications-dir and --with-frameworks-dir as ~/path/to/Applications, ~/path/to/Frameworks.

I was installing libsdl, when it got to python27 it failed:

--->  Staging python27 into destroot
Error: org.macports.destroot for port python27 returned: command execution failed
Error: Failed to install python27

the .conf files listed the prefix as /Users/name/path/to/macports, but applications_dir and frameworks_dir as ~/path/to/Applications, ~/path/to/Frameworks, respectively. These aren't expanded during port installation it seems.

Updating the .conf files to absolute paths, port clean python27, port install libsdl did the trick, correctly installing without errors.

I know it's up to the user when they start installing to other places, but perhaps this is somehow useful. Thanks.

[larryv (Lawrence Velázquez)]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

I believe this expansion for --prefix happens with this eval here: source:macports-base/configure.ac?rev=v2.12.4#L346​

If we wanted --applications-dir and --frameworks-dir to do this too, a similar eval would have to be added to MP_PATH_APPLICATIONS and MP_PATH_FRAMEWORKS in aclocal.m4.