MacPorts-1.6.0 installer postflight script

[lailoken3@…]

this is Leopard 10.5.2

1) line 36 assumes that the install is to the boot drive,

it does not take the selected installation drive into account

2) if there is no .profile &c

the script does not recognize the shell, an appropriate error message would be helpful.

3) saying to set up the environment manually isn't meaningful to a lot of people.

[jmr@…]

The failure when there is no .profile is fixed in the updated script that will ship in  1.6.1. Could you please check whether the other points apply to the  trunk version?

[raimue@…]

postflight in trunk is still broken. It was fixed on release_1_6 but not merged back into trunk.

[ryandesign@…]

Replying to raimue@…:

postflight in trunk is still broken. It was fixed on release_1_6 but not merged back into trunk.

Rainer copied postflight from the 1.6 branch to trunk in r38037.

[ryandesign@…]

Replying to lailoken3@…:

1) line 36 assumes that the install is to the boot drive, it does not take the selected installation drive into account

Line 36 of postflight in 1.6.0 is:

BINPATH=$PREFIX/bin

That is correct, since that's what we want to write into the .profile. The part that may appear incorrect is where we later use that to set the path to run port selfupdate:

export PATH=$BINPATH:$PATH
port -v selfupdate || {
    echo "An attempt to synchronize your recent MacPorts installation with the project's rsync server failed!"
    echo "Please run 'port -d selfupdate' manually to find out the cause of the error."
    exit 1
}

This has changed substantially in the postflight that's now in trunk. Now we have a function update_macports which does this:

    if ! ${BINPATH}/port -v selfupdate; then 
        echo "An attempt to synchronize your recent MacPorts installation with the project's rsync server failed!"
        echo "Please run 'sudo port -d selfupdate' manually to find out the cause of the error."
    else
        echo "Successful!"
    fi

This would be just as unsuccessful if you're not installing MacPorts on the boot drive.

Even if we change it at this point to prepend "$2" to ${BINPATH} to use the selected install drive instead of the boot drive, the selfupdate wouldn't work. There's no abstraction in port that would let it know to prepend some prefix to its own during install time. Even if there were, the selfupdate may download and compile a new version of MacPorts. If so, we would want that compilation to run on the destination operating system.

So in conclusion, the simplest correct thing to do at this point would be to prevent the disk image installer from installing on anything other than the boot drive.

[blb@…]

Unless done manually, this will require some work to package1.0/portpkg.tcl as it currently just sets various values (proc write_info_plist) in the package's Info.plist (IFPkgFlagRootVolumeOnly being the one we want set to true). The best method being to allow some kind of pkg.flag RootVolumeOnly=true in the Portfile, or something to that effect.

[jmr@…]

Changed IFPkgFlagRootVolumeOnly to always be true in r53250. I think the rest of this has been addressed now.