Date: Fri, 29 May 2009 11:52:52 -0600 (MDT) From: Warren Block <wblock@wonkity.com> To: Barry McCormick <barry@pdc4u.com> Cc: Michael Goodell <michael@pdc4u.com>, questions@freebsd.org Subject: Re: difference between cvsup and portsnap Message-ID: <alpine.BSF.2.00.0905291141450.42856@wonkity.com> In-Reply-To: <1243616981.26778.6.camel@bmac-desktop> References: <1243616981.26778.6.camel@bmac-desktop>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 29 May 2009, Barry McCormick wrote: > Here at my work we use FreeBSD in production. We have the following > debate and wish to know better the differences between cvsup(csup) and > portsnap. One of my co-workers think that portsnap should NOT be used > and only gets the latest and greatest port collection, no matter what > version of FreeBSD is on the server. For example, if you are still > running a 5.4 stable box in production and use any of the portsnap, > portupgrade, etc utilities, you would pull the current version ports and > NOT from teh directory of the 5.4 ports. I.E, risk breaking the > production box. So you should not use portsnap ever except for dev > boxes. The idea that there's a "5.4 ports" directory is mistaken. The ports tree isn't branched; note the lack of a "tag=" entry in the example ports-supfile. csup will let you retrieve from a certain date, but that's not normal usage for the ports tree. So check your ports-supfile. It's probably already retrieving the latest version of ports, just like portsnap. -Warren Block * Rapid City, South Dakota USA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0905291141450.42856>