selfupdate not respecting all installation options

[kencu (Ken)]

MacPorts previously respected all the install settings ( --applications-dir= --with-curlprefix= being the two I generally use in addition to --prefix) , but the new version 2.4.2 does not respect those when updating an existing installation. It does respect the previous --prefix setting, but not the others.

This was noted on several different machines, all of which have two installations of MacPorts, one in /opt/bootstrap and the one in /opt/local

[kencu (Ken)]

Original installation (from history):

48  ./configure --prefix=/opt/bootstrap --with-applications-dir=/opt/bootstrap/Applications
49  make && sudo make install

---

configuration of selfupdate

$ sudo /opt/bootstrap/bin/port -v selfupdate

<snip>
checking for Applications installation directory... /Applications/MacPorts
checking for Frameworks installation directory... /opt/bootstrap/Library/Frameworks

[kencu (Ken)]

full log of update install

[jmroot (Joshua Root)]

Not sure what to tell you; the configure script has not changed at all between 2.4.1 and 2.4.2 except for the version number. In a fresh build directory you will of course have to pass the appropriate options again; it won't magically know that it's updating an existing installation.

[kencu (Ken)]

It's not a fresh install, though -- previously, when I did a /opt/bootstrap/bin/port -v selfupdate, it appeared to pick up the build settings of that installation and respect them for the update. But now (AFAICT) it only respects --prefix.

K

[jmroot (Joshua Root)]

Oh, so this is specifically about selfupdate? You didn't really make that clear at first.

Anyway, applications_dir isn't a problem because the configure option only affects the value in macports.conf.default. As for with-curlprefix, I doubt that has ever been respected by selfupdate.

[kencu (Ken)]

OK. My guess is then that the selfupdate for the install in /opt/bootstrap might have picked up the macports.conf.default in /opt/local instead of the one in /opt/bootstrap.

If so, this would probably affect others who install more than one copy of MacPorts (which not that many people, to be sure).

As a related request, would be nice if selfupdate picked up all the original build configuration in a given installation of MacPorts.

[jmroot (Joshua Root)]

Replying to kencu:

OK. My guess is then that the selfupdate for the install in /opt/bootstrap might have picked up the macports.conf.default in /opt/local instead of the one in /opt/bootstrap.

Was there not a macports.conf in /opt/bootstrap? Nothing actually reads macports.conf.default, the only time it is used is to create macports.conf if it doesn't already exist.

If so, this would probably affect others who install more than one copy of MacPorts (which not that many people, to be sure).

As a related request, would be nice if selfupdate picked up all the original build configuration in a given installation of MacPorts.

I thought that was exactly what this ticket was already about?

[kencu (Ken)]

This is working correctly. I must have been mistaken previously when I thought those other installation options were respected.

[jmroot (Joshua Root)]

You can leave this open as a feature request if you need it. But if not that's also fine.