Date: Fri, 29 May 2009 14:03:37 -0400 From: Glen Barber <glen.j.barber@gmail.com> To: barry@pdc4u.com Cc: Michael Goodell <michael@pdc4u.com>, questions@freebsd.org Subject: Re: difference between cvsup and portsnap Message-ID: <4ad871310905291103w5ca1a8c3h67a6005b91f8a10e@mail.gmail.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
Hi, Barry On Fri, May 29, 2009 at 1:09 PM, Barry McCormick <barry@pdc4u.com> wrote: > Here at my work we use FreeBSD in production. =A0We have the following > debate and wish to know better the differences between cvsup(csup) and > portsnap. =A0One of my co-workers think that portsnap should NOT be used > and only gets the latest and greatest port collection, no matter what > version =A0of FreeBSD is on the server. =A0 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. =A0So you should not use portsnap ever except for dev > boxes. > Either way, with 5.X being EOL'd, there is no guarantee current ports will work. > I have always used portsnap to set up a new machine. =A0I have never had > it pull a wrong port that I knew of. =A0I think it has to pay attention t= o > the version of the ports it is pulling. > > > which is right? =A0This is a major issue with our production servers. > Thanks > Neither one is "right", per se. However, if you use one, continue to use _that_one_ to avoid conflicts. --=20 Glen Barber
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4ad871310905291103w5ca1a8c3h67a6005b91f8a10e>