Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 26 Jan 2013 23:34:15 -0500
From:      Lowell Gilbert <freebsd-questions-local@be-well.ilk.org>
To:        "W. D." <WD@US-Webmasters.com>
Cc:        freebsd-questions@FreeBSD.org
Subject:   Re: Cronjob Cvsup -> What?
Message-ID:  <44d2wrw8fs.fsf@lowell-desk.lan>
In-Reply-To: <20130127001805.97F0119B@hub.freebsd.org> (W. D.'s message of "Sat, 26 Jan 2013 18:11:14 -0600")
References:  <20130127001805.97F0119B@hub.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
"W. D." <WD@US-Webmasters.com> writes:

> According to:
>
>   http://www.freebsd.org/news/2012-compromise.html
>
> Cvsup is deprecated.  If I have a Cron entry like:
>
> #-----------------------------------------------------------------
> #Min   Hr    DOM   Mnth  DOW   Command
>
> #   At 3:46 in the morning, everyday, as root, update the ports tree:
> 46     3     *     *     *     /usr/local/bin/cvsup   -h   cvsup12.FreeBSD.org  /usr/share/examples/cvsup/ports-supfile 
> #-----------------------------------------------------------------
>
> What should I use: freebsd-update, Subversion, portsnap, or what?
>
> What would be the best Cron command to keep ports updated on a daily
> basis?

portsnap is almost certainly the best answer for you.

freebsd-update is for the base system, not ports. 

If you needed version control features on your ports tree (especially if
you were regularly contributing changes to ports), getting and updating
your tree through subversion would have some extra features you might
want, but it doesn't sound as if that is the case for you.

Unless you have a specific reason why portsnap doesn't fit your use
case, it's definitely the way to go for just keeping a ports tree
updated regularly.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44d2wrw8fs.fsf>