hmm, on Mon, Dec 03, 2007 at 06:49:19PM -0500, Mark Bucciarelli said that > On 12/3/07, Landry Breuil <[EMAIL PROTECTED]> wrote: > > > It has already been discussed, there is no one available to handle > > security updates to -stable ports. > > Missed that, I was searching on lighttpd. I have now read Nikolay's > message re: -stable. Too bad. :( > > > It is recommended to use -current > > if you want maintained ports with security updates. > > I am at 4.2 now. If I upgrade to the Nov. 26th snapshot, I must > rebuild all installed packages using the ports tree, correct? > > Must I rebuild all installed ports each time I update to a new > snapshot or via cvs up?
on production machines; if the dependencies are light, i prefer importing a newer version into /usr/ports and compiling just the particular software's newer version. keeping up with a -current package-wise in production is madness. suppose your customer wants X, 3 weeks after you upgraded to -current. the snapshots are long gone and you will have to compile it by hand anyway, so why not stay with release and have a couple of exceptions? YMMV. -f -- 1st law of thermodynamics: go to class!
