Looks good overall. I just have one comment about the appending to the .pdrc. Its a tough thing to handle overall, overwrite?, append?, skip if exists?. I guess it depends on the target audience. And since its for MacOS, the append is the best option for the default. But is there a way that the installer could ask a question, whether to overwrite, append, or ignore the .pdrc?
.hc
On Fri, 7 Mar 2003, Adam Lindsay wrote:
Hi folks.
I just wanted to do a sanity check for the postinstall script in my proposed MacOSX installer. It attempts to give a .tcshrc and .pdrc to those who don't already have them. Please, no flames about tcsh--it's still the default shell in MacOSX to the best of my knowledge, and it's the shell I know best.
The intention is to prep the command line for those who don't like to use it, but to be kind enough to people who are able to hack their own dotfiles (and not clobber anything too important, which is why everything is an append).
Comments before I turn this into a package?
#!/bin/tcsh
# root/realtime trick /usr/sbin/chown root /usr/local/pd/bin/pd /bin/chmod 4755 /usr/local/pd/bin/pd
# make a few home/Library directories for future expansion /bin/mkdir -p $HOME/Library/Pd/Help /bin/mkdir $HOME/Library/Pd/Externals /bin/mkdir $HOME/Library/Pd/AdditionalDocumentation
# add a path if ( ! `grep -sc /usr/local/pd/bin $HOME/.tcshrc` ) echo 'set path = ( / usr/local/pd/bin $path )' >>! $HOME/.tcshrc
echo -rt >>! $HOME/.pdrc echo -path ~/Library/Pd/Externals >> $HOME/.pdrc echo -helppath ~/Library/Pd/Externals >> $HOME/.pdrc echo -path /Library/Pd/Externals >> $HOME/.pdrc echo -helppath /Library/Pd/Externals >> $HOME/.pdrc echo -guishadow >> $HOME/.pdrc echo -cordcolor >> $HOME/.pdrc
--
Adam T. Lindsay atl@comp.lancs.ac.uk Computing Dept, Lancaster University +44(0)1524/594.537 Lancaster, LA1 4YR, UK Fax:+44(0)1524/593.608 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
PD-dev mailing list PD-dev@iem.kug.ac.at http://iem.kug.ac.at/cgi-bin/mailman/listinfo/pd-dev
zen \ \ \[D[D[D[D