Kernel Monkey <[EMAIL PROTECTED]> wrote: > I've been using the cvsup client to update my sources. What is the > difference between cvs and cvsup when updating sources?
CVS is a version control system. You can (ab)use it for source distribution purposes, but it is very inefficient in this role. CVSup is a generic mirroring tool that has special support for CVS repositories. Apart from efficiently mirroring a repository, it also supports "checkout mode" to retrieve a particular set of revisions--which is probably what you have been using when compare it to CVS. The problem with CVSup is that it is written in Modula-3 and its availability is limited to that of a Modula-3 compiler. There are further related tools: CVSync is a repository mirroring tool. There is no checkout mode. CSup is a CVSup client that only implements checkout mode. Also, a generic mirroring tool such as sup or rsync can be used to replicate CVS repositories. However, both CVSup and CVSync are more efficient at this task. If you just want to get the source tree, the CVSup protocol with the cvsup client or csup are most efficient. If you want to add your own changes to the source, or if you have a bunch of machines, in particular if they are on different branches (x.y-stable, -current), I would recommend that you get a copy of the repository through either CVSup or CVSync and then use cvs to check out the source trees from that local repository. In a LAN environment, simply mounting the repository over NFS and running a "local" checkout is worth considering. -- Christian "naddy" Weisgerber [EMAIL PROTECTED]
