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
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
It would be great if we had a configure panel for pd. someone wrote something like this, right ? Just can't remember the link.
Guenter
On Wed, 12 Mar 2003, Hans-Christoph Steiner wrote:
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
PD-dev mailing list PD-dev@iem.kug.ac.at http://iem.kug.ac.at/cgi-bin/mailman/listinfo/pd-dev
Hello, Hans-Christoph,
Hans-Christoph Steiner said this at Wed, 12 Mar 2003 21:41:10 -0800:
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.
That was my line of thinking, at least. If someone had something there, I didn't want to delete it, but I did want to make them "aware" of the new options.
But is there a way that the installer could ask a question, whether to overwrite, append, or ignore the .pdrc?
Not as such, when using Apple's installer. It *could* be in a separate package to select/unselect, but I suspect not a lot of users take advantage of the different sub-packages in the installer. Plus that would add more work to package maintenance.
What occurred to me after release is checking for the existence of "- helppath" in the .pdrc, so that I don't continually append with each upgrade. Duh. (Plus, one thing that I caught before release is that I mixed up the "Externals" and "Help" directories, below.
Thanks for the sanity check. Adam
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
On Thursday, Mar 13, 2003, at 04:58 America/New_York, Adam Lindsay wrote:
What occurred to me after release is checking for the existence of "- helppath" in the .pdrc, so that I don't continually append with each upgrade. Duh. (Plus, one thing that I caught before release is that I mixed up the "Externals" and "Help" directories, below.
If you are going to check for the existence of one tag, you might as well check the others too, like -cordcolor, -guishadow, -rt, etc. Another thing which might be helpful is including -listdev in every .pdrc so that it would be super easy to tell people how to look up their devices, for troubleshooting MIDI setup for example.
.hc
-
Adam Lindsay -
guenter geiger -
Hans-Christoph Steiner