At 23:11 9/24/2004, Donald J. O'Neill wrote:
>On Friday 24 September 2004 06:32 pm, Chris wrote:
>> W. D. wrote:
>> > At 14:44 9/23/2004, Chris, wrote:
>> >>>>You could join in the FreeBSD tradition, though, and do it
>> >>>> the Right Way(tm) ...
>> >>>>
>> >>>>http://www.onlamp.com/pub/a/bsd/2003/08/28/FreeBSD_Basics.htm
>> >>>>l
>> >>>>
>> >>>>An excellent tutorial/article by Dru Lavigne....
>> >>>>
>> >>>>Kevin Kinsey
>> >>>
>> >>>OK, after reading this tutorial, here is MY new WAY.
>> >>>
>> >>> /usr/local/bin/cvsup -g -L 2 /root/cvsup/ports-supfile
>> >>> portsdb -Uu
>> >>> portversion -l "<" [to see if any ports will be upgraded]
>> >>> portupgrade -arR [so dependencies will be installed, if
>> >>> necessary] [NB. If ever asked to run pkgdb -F, do it]
>> >>>
>> >>>Taking into consideration other issues or options pointed out
>> >>> on the web tutorial, will this be a good strategy from now on
>> >>> for performing good port upgrades?
>> >>>
>> >>>Curtis
>> >>
>> >>Yes - this is more or less how I do mine.
>> >>--
>> >>Best regards,
>> >>Chris
>> >
>> > OK, how about adding a cron job by root like this?
>> >
>> > (Line will wrap. Everything between '===' on one line)
>> > ==========================================================
>> > 15 3 * * * /usr/local/bin/cvsup -h cvsup7.FreeBSD.org
>> > /usr/share/examples/cvsup/ports-supfile && portsdb -Uu && pkgdb
>> > -fu && cd /usr/ports && make index
>> > ==========================================================
>> >
>> >
>> > Then in the morning running:
>> >
>> > portversion -l "<"
>> >
>> > Would this automate things without causing problems?
>> > Any other safe ways to automate the process?
>> >
>> >
>>
>> I tend to do this in a periodic cron. Under /etc/periodic/weekly.
>> That also includes the output of portversion to the email.
>>
>> Then in the morning, I run the upgrade.
><<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>
>Hey, I can get all of at once.
>
>W.D. it's your cron job I'm looking, so I'll talk about it. It would
>work, probably most of the time. Your example has both portsdb -Uu
>and make index in it. Just use one, otherwise you're building INDEX-5
>twice. Running pkgdb -fu (by the way, make that -uf instead, I know
>it doesn't make any difference but I look at it and laugh too hard
>to think about anything else)
Yeah, I guess we really want to un-eff the database, rather than
eff-up the database. ;^)
> won't do the trick in the case were
>you've deleted something and the now missing dependencies were not
>taken care of.
How would one know when this has occurred?
>You're going to have to do pkgdb -fF and manually
>remove the bad dependencies.
I am clueless here. How would one do this if/when
it would happen.
>The one place where I definitely
>remember this happening was the upgrade from kde32 to kde33.
>
>It's easy for someone to shoot down an idea, it's harder to come up
>with the idea in the first place.
So, are you saying that I should just do this in the cron job:
(Line will wrap. Everything between '===' is on one line)
==========================================================
15 3 * * * /usr/local/bin/cvsup -h cvsup7.FreeBSD.org
/usr/share/examples/cvsup/ports-supfile && pkgdb -uf && cd /usr/ports && make index
==========================================================
and then do this manually in the morning:
portversion -l "<"
and if necessary:
portupgrade -arR
Start Here to Find It Fast!™ -> http://www.US-Webmasters.com/best-start-page/
$8.77 Domain Names -> http://domains.us-webmasters.com/
_______________________________________________
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
