Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

cvs deprecated

7 views
Skip to first unread message

Wojciech Puchar

unread,
Dec 27, 2012, 4:18:47 AM12/27/12
to
but i can't find "moron guide" for using svn to update tree.

I never used cvs or svn myself just want to

1) get latest FreeBSD 9-* sources
2) get latest HEAD sources.

could someone just tell me what command (and/or config file) i have to use
today, as cvs will not work soon
_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hacke...@freebsd.org"

Garrett Cooper

unread,
Dec 27, 2012, 4:46:28 AM12/27/12
to
On Thu, Dec 27, 2012 at 1:18 AM, Wojciech Puchar
<woj...@wojtek.tensor.gdynia.pl> wrote:
> but i can't find "moron guide" for using svn to update tree.
>
> I never used cvs or svn myself just want to
>
> 1) get latest FreeBSD 9-* sources
> 2) get latest HEAD sources.

1. Checkout the sources:

cd /usr/src # Change to something else if you don't want to checkout
to /usr/src.
svn co http://svn.freebsd.org/base/stable/9 . # stable/9
svn co http://svn.freebsd.org/base/head . # CURRENT

2. Updating:

cd /usr/src # Same caveat as above.
svn up

See also: http://www.freebsd.org/doc/handbook/svn.html .

...

HTH,
-Garrett

Jack L.

unread,
Dec 27, 2012, 4:49:57 AM12/27/12
to
For svn, you can use

svn co svn://svn.freebsd.org/base/[whatever]

You can find all the [whatever] at http://svnweb.freebsd.org/base/

so if you wanted to get the latest HEAD src, then it would go something like

svn co svn://svn.freebsd.org/base/head


On Thu, Dec 27, 2012 at 1:18 AM, Wojciech Puchar
<woj...@wojtek.tensor.gdynia.pl> wrote:
> but i can't find "moron guide" for using svn to update tree.
>
> I never used cvs or svn myself just want to
>
> 1) get latest FreeBSD 9-* sources
> 2) get latest HEAD sources.
>
> could someone just tell me what command (and/or config file) i have to use
> today, as cvs will not work soon

Chris Rees

unread,
Dec 27, 2012, 5:30:01 AM12/27/12
to
On 27 Dec 2012 09:47, "Garrett Cooper" <yane...@gmail.com> wrote:
>
> On Thu, Dec 27, 2012 at 1:18 AM, Wojciech Puchar
> <woj...@wojtek.tensor.gdynia.pl> wrote:
> > but i can't find "moron guide" for using svn to update tree.
> >
> > I never used cvs or svn myself just want to
> >
> > 1) get latest FreeBSD 9-* sources
> > 2) get latest HEAD sources.
>
> 1. Checkout the sources:
>
> cd /usr/src # Change to something else if you don't want to checkout
> to /usr/src.
> svn co http://svn.freebsd.org/base/stable/9 . # stable/9
> svn co http://svn.freebsd.org/base/head . # CURRENT

I recall a cluster administrator advising use of svn protocol rather than
http. Something to do with overheads.

Chris

Garrett Cooper

unread,
Dec 27, 2012, 5:33:00 AM12/27/12
to
On Thu, Dec 27, 2012 at 2:30 AM, Chris Rees <uti...@gmail.com> wrote:
>
> On 27 Dec 2012 09:47, "Garrett Cooper" <yane...@gmail.com> wrote:
>>
>> On Thu, Dec 27, 2012 at 1:18 AM, Wojciech Puchar
>> <woj...@wojtek.tensor.gdynia.pl> wrote:
>> > but i can't find "moron guide" for using svn to update tree.
>> >
>> > I never used cvs or svn myself just want to
>> >
>> > 1) get latest FreeBSD 9-* sources
>> > 2) get latest HEAD sources.
>>
>> 1. Checkout the sources:
>>
>> cd /usr/src # Change to something else if you don't want to checkout
>> to /usr/src.
>> svn co http://svn.freebsd.org/base/stable/9 . # stable/9
>> svn co http://svn.freebsd.org/base/head . # CURRENT
>
> I recall a cluster administrator advising use of svn protocol rather than
> http. Something to do with overheads.

Yes, you're right. http opens a connection per-file, which is
horrendous with server load and is very slow as HTTP isn't optimized
for this purpose (and the current defacto HTTP library used with svn
isn't the most performant thing in the world). Unfortunately some
groups filter svn:// traffic though (like my employer), so I'm stuck
with http:// URIs for now (hence, the force of habit).
Thanks,
-Garrett

Garrett Cooper

unread,
Dec 27, 2012, 9:57:24 AM12/27/12
to
On Thu, Dec 27, 2012 at 6:50 AM, Warren Block <wbl...@wonkity.com> wrote:

...

> I see a lot of people switching to the target directory first rather than
> just including it as an argument for svn. Is there an advantage there that
> I'm missing? I've always just used
>
> svn co http://svn.freebsd.org/base/stable/9 /usr/src
>
> and
>
> svn up /usr/src

No difference really, other than the cumulative amount of typed
characters is less in the former form compared to the latter form.

Warren Block

unread,
Dec 27, 2012, 9:50:45 AM12/27/12
to
On Thu, 27 Dec 2012, Garrett Cooper wrote:

> On Thu, Dec 27, 2012 at 1:18 AM, Wojciech Puchar
> <woj...@wojtek.tensor.gdynia.pl> wrote:
>> but i can't find "moron guide" for using svn to update tree.
>>
>> I never used cvs or svn myself just want to
>>
>> 1) get latest FreeBSD 9-* sources
>> 2) get latest HEAD sources.
>
> 1. Checkout the sources:
>
> cd /usr/src # Change to something else if you don't want to checkout
> to /usr/src.
> svn co http://svn.freebsd.org/base/stable/9 . # stable/9
> svn co http://svn.freebsd.org/base/head . # CURRENT
>
> 2. Updating:
>
> cd /usr/src # Same caveat as above.
> svn up
>
> See also: http://www.freebsd.org/doc/handbook/svn.html .

I see a lot of people switching to the target directory first rather
than just including it as an argument for svn. Is there an advantage
there that I'm missing? I've always just used

svn co http://svn.freebsd.org/base/stable/9 /usr/src

and

svn up /usr/src

Warren Block

unread,
Dec 27, 2012, 10:11:52 AM12/27/12
to
On Thu, 27 Dec 2012, Garrett Cooper wrote:

> On Thu, Dec 27, 2012 at 6:50 AM, Warren Block <wbl...@wonkity.com> wrote:
>
> ...
>
>> I see a lot of people switching to the target directory first rather than
>> just including it as an argument for svn. Is there an advantage there that
>> I'm missing? I've always just used
>>
>> svn co http://svn.freebsd.org/base/stable/9 /usr/src
>>
>> and
>>
>> svn up /usr/src
>
> No difference really, other than the cumulative amount of typed
> characters is less in the former form compared to the latter form.

Ah, I see what you mean. Depends on whether you were going to cd into
the target directory immediately.

svn up can update multiple local working copies through one command,
too:

svn up /usr/src /usr/ports

RW

unread,
Dec 27, 2012, 10:28:04 AM12/27/12
to
On Thu, 27 Dec 2012 02:33:00 -0800
Garrett Cooper wrote:

> On Thu, Dec 27, 2012 at 2:30 AM, Chris Rees <uti...@gmail.com> wrote:
> >

> > I recall a cluster administrator advising use of svn protocol
> > rather than http. Something to do with overheads.
>
> Yes, you're right. http opens a connection per-file, which is
> horrendous with server load and is very slow as HTTP isn't optimized
> for this purpose

Presumably that's a limitation of the library or subversion because it's
not true of HTTP per se. Portsnap, for example, uses persistent
connections with pipelining.



> (and the current defacto HTTP library used with svn
> isn't the most performant thing in the world).


Garrett Cooper

unread,
Dec 27, 2012, 10:43:52 AM12/27/12
to
On Thu, Dec 27, 2012 at 7:28 AM, RW <rwmai...@googlemail.com> wrote:
> On Thu, 27 Dec 2012 02:33:00 -0800
> Garrett Cooper wrote:
>
>> On Thu, Dec 27, 2012 at 2:30 AM, Chris Rees <uti...@gmail.com> wrote:
>> >
>
>> > I recall a cluster administrator advising use of svn protocol
>> > rather than http. Something to do with overheads.
>>
>> Yes, you're right. http opens a connection per-file, which is
>> horrendous with server load and is very slow as HTTP isn't optimized
>> for this purpose
>
> Presumably that's a limitation of the library or subversion because it's
> not true of HTTP per se. Portsnap, for example, uses persistent
> connections with pipelining.

An example of what I mean [1]:

=======================

A checkout/update over svn:// is approx 4-12 times faster than over
http(s):// . The factor depends on number of files/folders and file
size . Apache is much slower on many small files because each file is
a full http-request-response cycle. In Tortoise you can easily see the
speed dropping:

Checkout a large java projects If you transfer a huge .jar, transfer
is going up, on getting source java files and creating package
structure, it will drop.

Also important is that svn checkout is slower on client than svn
export and also eclipse(java) is much slower than tortoise/CMD.
share|improve this answer

=======================

Qualitatively we (my group) have seen a huge performance increase in
our svnsyncs from freebsd.org using svn:// instead of http:// . We
haven't measured how much the difference is quantatively though
because a qualitative answer was sufficient for helping reinforce a
business case for unfiltering that port with corporate.

HTH,
-Garrett

1. http://stackoverflow.com/questions/372569/subversion-protocol-performance

Sam Fourman Jr.

unread,
Dec 27, 2012, 11:29:21 AM12/27/12
to
On Thu, Dec 27, 2012 at 4:18 AM, Wojciech Puchar
<woj...@wojtek.tensor.gdynia.pl> wrote:
> but i can't find "moron guide" for using svn to update tree.

I cant seem to find a way to handle conflicts, ive tried to do svn
revert on every directory, but there is always more... maybe svn just
isnt a good way to keep your ports tree current

svn up
Updating '.':
Skipped 'databases' -- Node remains in conflict
Skipped 'irc' -- Node remains in conflict
Skipped 'lang' -- Node remains in conflict
Skipped 'security/cyrus-sasl2' -- Node remains in conflict
Skipped 'x11/keybinder' -- Node remains in conflict
Skipped 'net-mgmt' -- Node remains in conflict
At revision 309546.
Summary of conflicts:
Skipped paths: 6

--

Sam Fourman Jr.

Sergey Matveychuk

unread,
Dec 27, 2012, 11:37:44 AM12/27/12
to
27.12.2012 20:29, Sam Fourman Jr. wrote:
> On Thu, Dec 27, 2012 at 4:18 AM, Wojciech Puchar
> <woj...@wojtek.tensor.gdynia.pl> wrote:
>> but i can't find "moron guide" for using svn to update tree.
>
> I cant seem to find a way to handle conflicts, ive tried to do svn
> revert on every directory, but there is always more... maybe svn just
> isnt a good way to keep your ports tree current
>
> svn up
> Updating '.':
> Skipped 'databases' -- Node remains in conflict
> Skipped 'irc' -- Node remains in conflict
> Skipped 'lang' -- Node remains in conflict
> Skipped 'security/cyrus-sasl2' -- Node remains in conflict
> Skipped 'x11/keybinder' -- Node remains in conflict
> Skipped 'net-mgmt' -- Node remains in conflict
> At revision 309546.
> Summary of conflicts:
> Skipped paths: 6
>

svn revert -R /usr/ports - works for me.

Garrett Cooper

unread,
Dec 27, 2012, 12:22:24 PM12/27/12
to
On Dec 27, 2012, at 8:37 AM, Sergey Matveychuk <s...@FreeBSD.org> wrote:

> 27.12.2012 20:29, Sam Fourman Jr. wrote:
>> On Thu, Dec 27, 2012 at 4:18 AM, Wojciech Puchar
>> <woj...@wojtek.tensor.gdynia.pl> wrote:
>>> but i can't find "moron guide" for using svn to update tree.
>>
>> I cant seem to find a way to handle conflicts, ive tried to do svn
>> revert on every directory, but there is always more... maybe svn just
>> isnt a good way to keep your ports tree current
>>
>> svn up
>> Updating '.':
>> Skipped 'databases' -- Node remains in conflict
>> Skipped 'irc' -- Node remains in conflict
>> Skipped 'lang' -- Node remains in conflict
>> Skipped 'security/cyrus-sasl2' -- Node remains in conflict
>> Skipped 'x11/keybinder' -- Node remains in conflict
>> Skipped 'net-mgmt' -- Node remains in conflict
>> At revision 309546.
>> Summary of conflicts:
>> Skipped paths: 6
>
> svn revert -R /usr/ports - works for me.

If you're checking out to a directory that already exists, svn resolved is the way to handle that. There might be (-> probably is) a way to check out the metadata by itself, but I can't verify how right now.
Hth,
-Garrett

Warren Block

unread,
Dec 27, 2012, 6:04:57 PM12/27/12
to
On Thu, 27 Dec 2012, Sam Fourman Jr. wrote:

> On Thu, Dec 27, 2012 at 4:18 AM, Wojciech Puchar
> <woj...@wojtek.tensor.gdynia.pl> wrote:
>> but i can't find "moron guide" for using svn to update tree.
>
> I cant seem to find a way to handle conflicts, ive tried to do svn
> revert on every directory, but there is always more... maybe svn just
> isnt a good way to keep your ports tree current
>
> svn up
> Updating '.':
> Skipped 'databases' -- Node remains in conflict
> Skipped 'irc' -- Node remains in conflict
> Skipped 'lang' -- Node remains in conflict
> Skipped 'security/cyrus-sasl2' -- Node remains in conflict
> Skipped 'x11/keybinder' -- Node remains in conflict
> Skipped 'net-mgmt' -- Node remains in conflict
> At revision 309546.
> Summary of conflicts:
> Skipped paths: 6

A checkout of the entire /usr/ports into an empty directory is the way
to start. You can save the distfiles directory out of an existing
/usr/ports first if desired. And any customizations to ports files, if
you have them.

Note that svn checkouts don't automatically combine. Checking out
/usr/ports is not equivalent to checking out all the category
subdirectories into /usr/ports.

Wojciech Puchar

unread,
Dec 29, 2012, 12:43:06 PM12/29/12
to
>
> 1. Checkout the sources:
>
> cd /usr/src # Change to something else if you don't want to checkout
> to /usr/src.
> svn co http://svn.freebsd.org/base/stable/9 . # stable/9
> svn co http://svn.freebsd.org/base/head . # CURRENT
>
> 2. Updating:
>
> cd /usr/src # Same caveat as above.
> svn up
>
> See also: http://www.freebsd.org/doc/handbook/svn.html .
>
seen but not found simple explanation which you gave me. Thank you very
much.

Wojciech Puchar

unread,
Dec 30, 2012, 7:57:58 AM12/30/12
to
do ports have to be updated this way or i can use portsnap as today? will
portsnap be continued or is too deprecated?

Chris Rees

unread,
Dec 30, 2012, 8:18:37 AM12/30/12
to
On 30 Dec 2012 12:58, "Wojciech Puchar" <woj...@wojtek.tensor.gdynia.pl>
wrote:
>
> do ports have to be updated this way or i can use portsnap as today? will
portsnap be continued or is too deprecated?

Portsnap is staying.

Chris

RW

unread,
Dec 30, 2012, 11:06:56 AM12/30/12
to
On Sun, 30 Dec 2012 13:18:37 +0000
Chris Rees wrote:

> On 30 Dec 2012 12:58, "Wojciech Puchar"
> <woj...@wojtek.tensor.gdynia.pl> wrote:
> >
> > do ports have to be updated this way or i can use portsnap as
> > today? will
> portsnap be continued or is too deprecated?
>
> Portsnap is staying.

And I understand that freebsd-update can be configured to only update
the base system source code. If you don't want development branches you
can do without subversion altogether.
0 new messages