Re: svn ports, or the hen egg
On 19/12/2013 08:04, Freddie Cash wrote: On Wed, Dec 18, 2013 at 1:09 PM, Matthias Apitz g...@unixarea.de wrote: Ok, thanks; but see this: $ uname -a FreeBSD tiny-r255948 10.0-ALPHA4 FreeBSD 10.0-ALPHA4 #1: Fri Oct 18 12:10:57 CEST 2013 g...@aurora.sisis.de:/usr/obj/usr/src/sys/GENERIC/i386 $ svnlite Type 'svn help' for usage. $ svn help svn: not found ​And ... if you type svnlite help what happens? The name of the command is svnlite, not svn, so you may have to mentally swap the terms in terminal messages. :)​ That would work once you know you need to use svnlite. Most people will try svn and after that fails look for a way to install it, rather than looking for a renamed substitute. Maybe a /bin/svn script could test if svn exists and exec it or svnlite or display a message that svnlite is available until svn is installed. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: svn ports, or the hen egg
I had (still have) svn on a USB-stick installation of FreeBSD 9.2-STABLE. So I tried to use that to checkout the src tree for FreeBSD-HEAD; re(4) recognized my on-motherboard (MSI Z77 MPOWER) Ethernet but couldn't connect. So, after NetBSD 6.1_STABLE hung consistently on boot, NetBSD-current amd64 booted and connected the Ethernet through NetBSD's re(4). So I checked out (cvs) NetBSD src and pkgsrc trees, updated system and packages, subsequently built subversion from pkgsrc. Then I checked out FreeBSD src tree successfully, and was successful building the new FreeBSD from the USB-stick installation of 9.2-STABLE amd64, and I use that for src, doc and ports trees until I can build devel/subversion in FreeBSD, am having some troubles there, can try again without tests and tools options to see if I was overambitious in selecting build options. Now I have wi-fi working through Hiro H50191 USB-stick adapter, device rsu. Tom ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
svn ports, or the hen egg
Hi, As ports are now for some time are to be pulled out via SVN (and not CVS) and the svn client is only in the ports tree and not in the base system, how is this thought to work in a clean way, without dusting the system before with some binary packages, only based on base system and sources? Thanks matthias -- Sent from my FreeBSD netbook Matthias Apitz, g...@unixarea.de, http://www.unixarea.de/ f: +49-170-4527211 UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: svn ports, or the hen egg
On 12/18/13 14:50, Matthias Apitz wrote: Hi, As ports are now for some time are to be pulled out via SVN (and not CVS) and the svn client is only in the ports tree and not in the base system, how is this thought to work in a clean way, without dusting the system before with some binary packages, only based on base system and sources? Thanks matthias There's svnlite in -CURRENT now. -Nathan ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: svn ports, or the hen egg
On Wed, Dec 18, 2013 at 12:50 PM, Matthias Apitz g...@unixarea.de wrote: As ports are now for some time are to be pulled out via SVN (and not CVS) and the svn client is only in the ports tree and not in the base system, how is this thought to work in a clean way, without dusting the system before with some binary packages, only based on base system and sources? svnlite is included in the base OS for 10.0. See https://wiki.freebsd.org/WhatsNew/FreeBSD10 for details. And http://svnweb.freebsd.org/base?view=revisionrevision=251886 for the commit message. -- Freddie Cash fjwc...@gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: svn ports, or the hen egg
On 18 Dec 2013, at 21:50, Matthias Apitz g...@unixarea.de wrote: As ports are now for some time are to be pulled out via SVN (and not CVS) and the svn client is only in the ports tree and not in the base system, how is this thought to work in a clean way, without dusting the system before with some binary packages, only based on base system and sources? Use portsnap, or if you use 10.x or later, the base system has svnlite. -Dimitry signature.asc Description: Message signed with OpenPGP using GPGMail
Re: svn ports, or the hen egg
On Wed, Dec 18, 2013 at 09:50:27PM +0100, Matthias Apitz wrote: Hi, As ports are now for some time are to be pulled out via SVN (and not CVS) and the svn client is only in the ports tree and not in the base system, how is this thought to work in a clean way, without dusting the system before with some binary packages, only based on base system and sources? Thanks matthias -- Sent from my FreeBSD netbook Matthias Apitz, g...@unixarea.de, http://www.unixarea.de/ f: +49-170-4527211 UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org First svn is in base named svnlite since 10, then the recommanded way to get the ports tree is to use portsnap which is also in base. regards, Bapt pgp0U7nk0bMpB.pgp Description: PGP signature
Re: svn ports, or the hen egg
El día Wednesday, December 18, 2013 a las 12:59:16PM -0800, Freddie Cash escribió: On Wed, Dec 18, 2013 at 12:50 PM, Matthias Apitz g...@unixarea.de wrote: As ports are now for some time are to be pulled out via SVN (and not CVS) and the svn client is only in the ports tree and not in the base system, how is this thought to work in a clean way, without dusting the system before with some binary packages, only based on base system and sources? svnlite is included in the base OS for 10.0. See https://wiki.freebsd.org/WhatsNew/FreeBSD10 for details. And http://svnweb.freebsd.org/base?view=revisionrevision=251886 for the commit message. Ok, thanks; but see this: $ uname -a FreeBSD tiny-r255948 10.0-ALPHA4 FreeBSD 10.0-ALPHA4 #1: Fri Oct 18 12:10:57 CEST 2013 g...@aurora.sisis.de:/usr/obj/usr/src/sys/GENERIC/i386 $ svnlite Type 'svn help' for usage. $ svn help svn: not found :-) matthias -- Sent from my FreeBSD netbook Matthias Apitz, g...@unixarea.de, http://www.unixarea.de/ f: +49-170-4527211 UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: svn ports, or the hen egg
On Wed, Dec 18, 2013 at 1:09 PM, Matthias Apitz g...@unixarea.de wrote: El día Wednesday, December 18, 2013 a las 12:59:16PM -0800, Freddie Cash escribió: On Wed, Dec 18, 2013 at 12:50 PM, Matthias Apitz g...@unixarea.de wrote: As ports are now for some time are to be pulled out via SVN (and not CVS) and the svn client is only in the ports tree and not in the base system, how is this thought to work in a clean way, without dusting the system before with some binary packages, only based on base system and sources? svnlite is included in the base OS for 10.0. See https://wiki.freebsd.org/WhatsNew/FreeBSD10 for details. And http://svnweb.freebsd.org/base?view=revisionrevision=251886 for the commit message. Ok, thanks; but see this: $ uname -a FreeBSD tiny-r255948 10.0-ALPHA4 FreeBSD 10.0-ALPHA4 #1: Fri Oct 18 12:10:57 CEST 2013 g...@aurora.sisis.de:/usr/obj/usr/src/sys/GENERIC/i386 $ svnlite Type 'svn help' for usage. $ svn help svn: not found And ... if you type svnlite help what happens? The name of the command is svnlite, not svn, so you may have to mentally swap the terms in terminal messages. :) -- Freddie Cash fjwc...@gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: svn ports, or the hen egg
On 2013-12-18 22:09, Matthias Apitz wrote: El día Wednesday, December 18, 2013 a las 12:59:16PM -0800, Freddie Cash escribió: On Wed, Dec 18, 2013 at 12:50 PM, Matthias Apitz g...@unixarea.de wrote: As ports are now for some time are to be pulled out via SVN (and not CVS) and the svn client is only in the ports tree and not in the base system, how is this thought to work in a clean way, without dusting the system before with some binary packages, only based on base system and sources? svnlite is included in the base OS for 10.0. See https://wiki.freebsd.org/WhatsNew/FreeBSD10 for details. And http://svnweb.freebsd.org/base?view=revisionrevision=251886 for the commit message. Ok, thanks; but see this: $ uname -a FreeBSD tiny-r255948 10.0-ALPHA4 FreeBSD 10.0-ALPHA4 #1: Fri Oct 18 12:10:57 CEST 2013 g...@aurora.sisis.de:/usr/obj/usr/src/sys/GENERIC/i386 $ svnlite Type 'svn help' for usage. $ svn help svn: not found :-) One of my first commands until svn is is installed $ alias svn svnlite -- olli ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
