Date: Sun, 27 Jan 2013 08:22:02 -0500 From: "Thomas Mueller" <mueller6724@bellsouth.net> To: freebsd-ports@freebsd.org Cc: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> Subject: Re: Cronjob Cvsup -> What? Message-ID: <C2.02.10746.AF925015@smtp02.insight.synacor.com>
next 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? Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> responds: > 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. I've always used "portsnap fetch update" after the initial "portsnap fetch" and "portsnap extract". What would be the adverse side effect of using svn instead? Tom
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C2.02.10746.AF925015>