On Sun, Mar 14, 2004 at 01:40:16AM +0100, Martin Costabel wrote:
> I have written a new pathsetup utility "pathsetup.sh" that is meant to 
> replace the "pathsetup.command" script. It does the same things as the 
> old version, but it has a new interface: Following hints by Bill Scott, 
> I replaced the Terminal.app window by AppleScript-generated dialog 
> windows. This should eliminate the bug where the pathsetup.command 
> hijacked the Terminal.app windows.

Excellent!

> Another difference to the previous version is that it is no longer 
> double-clickable, but I have the impression that this was never 
> important anyway. The pathsetup script is run in two ways: Either by the 
> Fink binary installer, where it is called from a perl script via the 
> "system" function, or directly from the command line. In both cases, the 
> shell script in /sw/bin is used, not the double-clickable contraption on 
> the surface of the Fink Installer dmg. The latter would just disappear 
> with the new version.

If an admin is trying to enable fink for a new user, he'd want to run
this. Given that having a GUI-ish interface means you're targetting
folks who may not be comfortable with CLI, keeping a double-clickable
thing (even if it's just an AppleScript applet or a thing.command or
maybe pathsetup.command so we don't have to change the docs:) that
runs the new pathsetup.sh) might be polite

dan

-- 
Daniel Macks
[EMAIL PROTECTED]
http://www.netspace.org/~dmacks



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to