Re: port management practices

2008-04-22 Thread christopher
On Wed, 23 Apr 2008 00:29:49 +0200 Ravna <[EMAIL PROTECTED]> wrote: > It's my philosophy, that a little each day, is better than lots, once in > a while. > Cron updates my ports tree every night and does a "portupgrade -a" > after that. > The output is saved to a file, so I can deal with proble

Re: port management practices

2008-04-22 Thread Matthew D. Fuller
On Sun, Apr 20, 2008 at 09:17:17PM -0700 I heard the voice of christopher, and lo! it spake thus: > > I know about csup, portupgrade, etc., and I think they are great, > but if you only have one app that you want to upgrade because it was > buggy at a previous time, then it doesn't seem like a pra

Re: port management practices

2008-04-22 Thread Ravna
It's my philosophy, that a little each day, is better than lots, once in a while. Cron updates my ports tree every night and does a "portupgrade -a" after that. The output is saved to a file, so I can deal with problems. I do a "buildworld/buildkernel" every week, if there are changes in the s

Re: port management practices

2008-04-22 Thread christopher
On Tue, 22 Apr 2008 08:02:06 -0700 Brian <[EMAIL PROTECTED]> wrote: > Jason C. Wells wrote: > > I don't. > > > > It's too much work. I don't update ports for the duration of a > I suppose this is relative to the number of ports installed, but it > really isnt that difficult under normal circums

Re: port management practices

2008-04-22 Thread Brian
Jason C. Wells wrote: I don't. It's too much work. I don't update ports for the duration of a major release's life. What ever ports came out for 6.3 (that's when I quit trying to manage ports) are typically what I am running. When 7.1 is released (I don't run x.0 releases) I will reinstall