Re: svn and/or portsnap
Regarding my question, How do you get the ports tree or svn in that case if not using portsnap? Helmut Schneider had two suggestions: You install ports from CD/DVD. Or use pkg_add -r subversion. :) ftp://ftp.freebsd.org/pub/FreeBSD/ports/ports/ I guess I could use the latter and then build subversion among other ports, then subsequently switch to svn. This would also work, I would guess, if ports tree is installed by bsdinstall or sysinstall. Question arises whether the ports tree as downloaded in tarball by ftp would be compatible/in sync with portsnap or svn. If in any doubt, either delete /usr/ports/* or move to /usr/ports-by-ftp and then restart fresh with svn. I noticed the FreeBSD Handbook ports section was not up-to-date on the use of subversion with the ports tree. Maybe with subversion now being elevated in importance for updating system source code and ports tree, it could become part of the base system. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: svn and/or portsnap
On Sun, 9 Sep 2012 10:37:03 + (UTC), Helmut Schneider wrote: Hi, I'm running a custom kernel so I (guess I) need svn in future to fetch sources instead of cvsup. Should I still use portsnap then for ports or also fetch them via svn? Polytropon responded: Ports and system sources are managed independently. You can use whatever tool you want. Note that portsnap _might_ not deliver the most current ports tree for a given point in time. For short time deltas, CVS has often proven to be the better tool, but of course portsnap has significant advantages (e. g. faster for longer pauses between ports tree updates, better integration with make update target). Depending on your updating habits, choose the tool that works best for you. One question comes up that I didn't think of immediately. How do you use svn on a fresh install of FreeBSD, no ports yet? svn/subversion is not part of the base system. How do you get the ports tree or svn in that case if not using portsnap? Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: svn and/or portsnap
On Tue, Sep 11, 2012 at 10:15 AM, Thomas Mueller muelle...@insightbb.com wrote: How do you get the ports tree or svn in that case if not using portsnap? You use pkg_add (or the youngest newcomer pkg) -- chs, ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: svn and/or portsnap
Thomas Mueller wrote: On Sun, 9 Sep 2012 10:37:03 + (UTC), Helmut Schneider wrote: Hi, I'm running a custom kernel so I (guess I) need svn in future to fetch sources instead of cvsup. Should I still use portsnap then for ports or also fetch them via svn? Polytropon responded: Ports and system sources are managed independently. You can use whatever tool you want. Note that portsnap might not deliver the most current ports tree for a given point in time. For short time deltas, CVS has often proven to be the better tool, but of course portsnap has significant advantages (e. g. faster for longer pauses between ports tree updates, better integration with make update target). Depending on your updating habits, choose the tool that works best for you. One question comes up that I didn't think of immediately. How do you use svn on a fresh install of FreeBSD, no ports yet? You install ports from CD/DVD. Or use pkg_add -r subversion. :) svn/subversion is not part of the base system. How do you get the ports tree or svn in that case if not using portsnap? ftp://ftp.freebsd.org/pub/FreeBSD/ports/ports/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: svn and/or portsnap
On Tue, 11 Sep 2012 04:15:24 -0400, Thomas Mueller wrote: One question comes up that I didn't think of immediately. How do you use svn on a fresh install of FreeBSD, no ports yet? svn/subversion is not part of the base system. How do you get the ports tree or svn in that case if not using portsnap? As this is an O(1) kind of problem, I'd suggest the easiest way: Use the package for svn. Install svn via # pkg_add -r svn (or however the svn package is called) and then use it to incorporate the full ports tree (and maybe also bring your OS sources to the branch you want, patched RELEASE, STABLE or HEAD). Afterwards, upgrade svn with the version from the ports tree which will possibly be newer. Then continue using ports to install software as usual. When CVS was not part of the OS, I went the same way by installing cvsup-without-x11 (or how the package was called) to be able to update ports and sources via CVS. Today this is not needed anymore, as CVS (as csup) is part of the OS. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
svn and/or portsnap
Hi, I'm running a custom kernel so I (guess I) need svn in future to fetch sources instead of cvsup. Should I still use portsnap then for ports or also fetch them via svn? Thanks, Helmut ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: svn and/or portsnap
On Sun, 9 Sep 2012 10:37:03 + (UTC), Helmut Schneider wrote: Hi, I'm running a custom kernel so I (guess I) need svn in future to fetch sources instead of cvsup. Should I still use portsnap then for ports or also fetch them via svn? Ports and system sources are managed independently. You can use whatever tool you want. Note that portsnap _might_ not deliver the most current ports tree for a given point in time. For short time deltas, CVS has often proven to be the better tool, but of course portsnap has significant advantages (e. g. faster for longer pauses between ports tree updates, better integration with make update target). Depending on your updating habits, choose the tool that works best for you. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: svn and/or portsnap
Polytropon wrote: On Sun, 9 Sep 2012 10:37:03 + (UTC), Helmut Schneider wrote: Hi, I'm running a custom kernel so I (guess I) need svn in future to fetch sources instead of cvsup. Should I still use portsnap then for ports or also fetch them via svn? Ports and system sources are managed independently. You can use whatever tool you want. The question should read: If I need to install svn anyway, is there an advantage of portsnap over svn to fetch ports. Note that portsnap might not deliver the most current ports tree for a given point in time. For short time deltas, CVS has often proven to be the better tool, but of course portsnap has significant advantages (e. g. faster for longer pauses between ports tree updates, better integration with make update target). Depending on your updating habits, choose the tool that works best for you. Currently I'm updating ports and src twice a day so I will keep using svn for both. Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: svn and/or portsnap
On Sun, 9 Sep 2012 11:26:50 + (UTC), Helmut Schneider wrote: Polytropon wrote: On Sun, 9 Sep 2012 10:37:03 + (UTC), Helmut Schneider wrote: Hi, I'm running a custom kernel so I (guess I) need svn in future to fetch sources instead of cvsup. Should I still use portsnap then for ports or also fetch them via svn? Ports and system sources are managed independently. You can use whatever tool you want. The question should read: If I need to install svn anyway, is there an advantage of portsnap over svn to fetch ports. As I said, it depends. If you don't update regularly (in short time spans), portsnap might be faster than SVN (to incorporate all the deltas). If you feel comfortable with this approach, you can keep using it. I don't see a general advantage here. Note that portsnap might not deliver the most current ports tree for a given point in time. For short time deltas, CVS has often proven to be the better tool, but of course portsnap has significant advantages (e. g. faster for longer pauses between ports tree updates, better integration with make update target). Depending on your updating habits, choose the tool that works best for you. Currently I'm updating ports and src twice a day so I will keep using svn for both. Good choice, in that case you won't have any advantage using portsnap as smaller amounts of deltas are no big deal when using SVN (or traditional CVS). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: svn and/or portsnap
On Sun, Sep 9, 2012 at 1:26 PM, Helmut Schneider jumpe...@gmx.de wrote: Currently I'm updating ports and src twice a day so I will keep using svn for both. While you certainly can, isn't it a bit excessive to update so frequently? Remember, it's not just fetching the sources and ports, you must also compile world _and_ ports if you want to stay current. I highly doubt that you want to do this twice a day, even on a very fast machine. And if you don't compile twice a day, it may be better to keep sources (and ports) with the installed binaries in sync. Just in case you need to investigate security breaches or buggy programs -- then you'll be glad to have the _corresponding_ sources available instead of some sources for binaries you have not installed yet. Thanks. Regards, -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: svn and/or portsnap
C. P. Ghost wrote: On Sun, Sep 9, 2012 at 1:26 PM, Helmut Schneider jumpe...@gmx.de wrote: Currently I'm updating ports and src twice a day so I will keep using svn for both. While you certainly can, isn't it a bit excessive to update so frequently? Remember, it's not just fetching the sources and ports, you must also compile world and ports if you want to stay current. I highly doubt that you want to do this twice a day, even on a very fast machine. I meant I fetch sources for src and ports twice a day. While ports helps me to track most recent changes src indeed might not require an update twice a day. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
