OK, no news is good news, I guess :-)
Martin Costabel wrote: []
Such a CLI version of pathsetup.sh is now in my exp directory. Please test.
Dave has now put this version into the latest fink from cvs, so I hope it will get some testing automatically.
Since the pathsetup script run by the Fink installer and the pathsetup.app that comes on the Fink installer dmg should still use Finder dialog popup windows, this would mean that /sw/bin/pathsetup.sh and pathsetup.app/Contents/MacOS/pathsetup would no longer be identical and the installer should run the latter.>
A couple of lines in some scripts in scripts/installer would have to be be edited to take this into account. In particular, scripts/installer/buildpkg.sh and scripts/installer/resources/postflight would need to be changed. I am not sure if any changes in the documentation would be needed.
Some more explanations: The previous "GUI" version would have to be put into pathsetup.app/Contents/MacOS/pathsetup directly and then the postflight script in the installer would work if the line
system "/sw/bin/pathsetup.sh; osascript -e 'tell application \"Installer\"' -e 'activate' -e 'end tell'";
is replaced by the two lines
my $package_path = $ENV{PACKAGE_PATH};
system "open -a \"$package_path\"/../pathsetup.app; osascript -e 'tell application \"Installer\"' -e 'activate' -e 'end tell'";
Since all this is rather complicated and more difficult to maintain than previously, I have made another "fat" version of the pathsetup shell script. This version looks first whether it is being run by someone who is allowed to make Finder popup windows (in particular whether it is being run by the Fink installer). If yes, it runs the "old" GUI version; if no, it runs the "new" CLI version.
This "fat" version can be used as previously, that is, it can be put as "pathsetup.sh" into /sw/bin/ and can be run from there either from the command line or by the Fink installer, or it can be put as "pathsetup" into pathsetup.app/Contents/MacOS/ and can be run by double-clicking the icon.
This new version is in my exp directory as "pathsetup_fat.sh". I have tested it in various different situations, but it would be useful if others could test it, too, before it is dumped on the unsuspecting users.
P.S. There is one situation where the (old and new) pathsetup script as run from the Fink installer fails: I think it happens only when the user "root" has tcsh as his login shell and the user who runs the installer has bash as his login shell. There is then an error message of the type "Sorry, I tried my best, but it doesn't work". In reality, this error message is bogus and the path is correctly set up. Therefore I think we can live with this bug (which would be hard to eliminate, since it happens only when the pathsetup script is run from a setuid root application as is the case in the Fink installer). This problem may have come up once on the lists. If it comes up more often, it would be easier to write a FAQ entry than to fix it :-)
-- Martin
------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
