installation sequence

[Michael Powell]

PJ wrote:

[snip]
> 
> Ok, I normally do something like that... problem here was that I made
> the mistake of thinking that an interesting little script I found was
> good for updating... but, I was sadly mistaken. The error was due to a
> badly downloaded ports tree. That fixed, all works fine.
> I really only have problems when some extraneous garbage comes along and
> I'm suckere in to try it.
> Here's the script (I modified it and it seems to work just fine) but I
> sure would like to hear if that makes sense.
> I called it update.ports and it runs from any directory. It can be
> changed to update source and docs if so desired or all could be done
> from same script.  Let me know, please, if it's ok?
> ======
> #!/bin/sh
> #
> # Update source, docs and ports
> 
> LOCAL_DIR="$(pwd)"
> 
> cd /usr/share/examples/cvsup
> csup ports-supfile
> cd /usr/ports
> make fetchindex
> 
> /usr/local/sbin/portsdb -u
> /usr//local/sbin/pkgdb -uvF
> 
> cd $LOCAL_DIR
> =======
> 

I essentially do something very similar. About once a week I do this:

csup -L 2 ports && portsdb -uF && pkgdb -u && portversion

This pretty much does the same thing as the script.

I keep intending to make it a cron job and email me the output, but until I 
get 'round to it I just take a quick gander at the output and if needed 
issue a portupgrade -a. 9.8 times out of 10 this is all I ever need. Every 
once in a while I have to manually fix something, but that isn't all that 
often, maybe once or twice a year. Another thing is to read UPDATING 
religiously as this can help sidestep boo boos before they happen.

[snip]

-Mike