From: Greg Ercolano <erco@(email surpressed)>
Subject: Re: nuke
   Date: Fri, 25 Feb 2011 20:41:37 -0500

Daniel Browne wrote:
> elsif ( $G::ismac )
> {
>     ### MAC
>     $ENV{PATH}    = "/Applications/Nuke5.1v5/Nuke5.1v5.app/Contents/MacOS:$ENV{PATH}";
>     $ENV{NUKECMD} = "Nuke5.1v5";
> }

	This is true in the newer scripts.

	But some older submit-nuke scripts didn't have the $ENV{NUKECMD} setting
	at the top, and were left to their own devices to set the nuke command.

	Nuke used to just be called 'nuke'. But then they changed that somewhere
	along the line so that the executable name had the version number in it.

	I mentioned to one of their software guys (not Bill Spitzak) they should
	at least have the regular command 'nuke' command in there as well,
	so that users can have just 'nuke' in their scripts, and just adjust
	their PATH to point to the correct version. This is what all other products
	do and it works fine.. but they seemed intent on having the version number
	in the executable name, which means that not only the PATH but the executable
	name must change as well. :(

-- 
Greg Ercolano, erco@(email surpressed)
Seriss Corporation
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)ext.23
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)