Bazaar

Bazaar

 




Wiki Tools

  • Find Page
  • Recent Changes
  • Page History
  • Attachments

Differences between revisions 67 and 68
Revision 67 as of 2006-08-06 08:34:42
Size: 7891
Comment: Bazaar-NG => Bazaar
Revision 68 as of 2006-08-06 12:30:12
Size: 8130
Editor: MatthieuMoy
Comment: Partial checkouts were described but not mentionned in comparison
Deletions are marked like this. Additions are marked like this.
Line 15: Line 15:
||Partial Checkouts ||<#ff8888>No ||<#ff8888>No ||<#88ff88>Yes ||<#88ff88>Yes ||<#dddddd>No? ||<#dddddd>No? ||<#dddddd>? ||<#dddddd>No? ||
Line 20: Line 21:
||Has Special Server ||<#ff8888>No  ||<#ff8888>No ||<#88ff88>Yes ||<#88ff88>Yes ||<#88ff88>Yes ||<#88ff88>Yes||<#88ff88>Yes ||<#88ff88>Yes || ||Has Special Server ||<#ff8888>Soon ||<#ff8888>No ||<#88ff88>Yes ||<#88ff88>Yes ||<#88ff88>Yes ||<#88ff88>Yes||<#88ff88>Yes ||<#88ff88>Yes ||
Line 77: Line 78:
The current implementation of Bazaar has very poor network performance for propagating changes. This is expected to become about 30 times faster in the near future. The current implementation of Bazaar has not excellent network performance for propagating changes (it already has improved much in the switch from weave format to knits format). This is expected to become about 30 times faster in the near future.

This chart is a rough draft

This page is a user-oriented comparison of different revision control system. For a more technical comparison, see ["RCSChoices"]. See also ["SCMComparisons"] (note: this may be better to move the content of this page here) for a brief presentation of each system and how they compare to Bazaar in particular. The determination on this chart is based upon the core installation and features that are already working in devel.

Overview

RCS Name

Bazaar

Arch

CVS

Subversion

Git

Mercurial

Monotone

Darcs

Decentralized

Yes

Yes

No

No

Yes

Yes

Yes

Yes

Disconnected Ops

Yes

Yes

No

Limited

Yes

Yes

Yes

Yes

Simple Namespace

Yes

No

No

Yes

No

No

No

Yes

Supports Renames

Yes

Yes

No

Somewhat

Somewhat

Somewhat

Yes

Yes

Needs Repository

No

Yes

Yes

Yes

No

No

Yes

No

Supports Repository

Yes

Yes

Yes

Yes

No

No

Yes

?

Checkouts

Yes

Yes

Yes

Yes

?

No

Yes

No

Partial Checkouts

No

No

Yes

Yes

No?

No?

?

No?

Atomic Commit

Yes

Yes

No

Yes

Yes

Yes

Yes

Yes

Cheap branching Anywhere

Yes

Yes

No

Yes

Yes

No

No

No

[:Merge:Smart Merge]

Yes

Yes

No

No

Yes

Yes

Yes

Yes

[:CherryPick:Cherrypicks]

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

[:BzrPlugins:Plugins]

Yes

No

No

?

?

Yes

?

No

Has Special Server

Soon

No

Yes

Yes

Yes

Yes

Yes

Yes

Req. Dedicated Server

No

No

Remote

Remote

No

No

No

No

Good Windows support

Yes

No

Yes

Yes

No

Somewhat

Yes

Yes

Fast Local Performance

Yes

No

Yes

Yes

Yes

Yes

Yes

No

Fast Network Performance

Soon

No

Yes

Yes

Yes

Yes

Yes

No

Details about each feature

Decentralized

Whether the tool is designed to allow [:Branch:branches] of the same project to be in different remote [:Repository:repositories].

Simple Namespace

The namespace is the way the RCS communicates with the user the various resources for the RCS such as the names for branches and the names for [:Revision:revisions] that are [:Merge:merge]. For example: requiring the user to refer to revisions with base-16 numbers is not considered "simple" in this document.

Needs Repository / Supports Repository

Some revision control systems require that branches be aggregated into [:Repository:repositories]. Bzr can use repositories if you like, for greater space efficiency, convenient publishing and backups.

Supports Renames

If a user can rename a file in the RCS without loosing the RCS history for a file, then renames are considered supported. If the operation resultes in a delete/add (aka "DA pair"), then renames are not considered supported. If the operation results in a copy/delete pair, renames are considered "somewhat" supported. The problem with copy support is that it is hard to define sane merge semantics for copies.

Has Checkouts

A ["Checkout"] is a [:WorkingTree:working tree] that points elsewhere for its RCS data.

Atomic Commit

Does the RCS track which files were associated with which [:Commit:commit].

Smart Merge

Whether the tool is able to know which revisions have to be merged (recording [:Merge:merge] history is a necessary condition for this).

Cheap Branching Anywhere

Some systems only support cheap branching on filesystems that support hard links, but bzr can do cheap branching on any filesystem, and even on FTP servers.

Cherrypicks

Whether the tool allows CherryPick (fine-grained selection of revisions to be merged).

Plugins

Whether the tool is extensible with plugins. Our plugins are on the BzrPlugins page.

Can use standard fileserver

Whether the tool can work with a standard file server (HTTP for read-only operations, ftp/sftp/webdav or others for write operations). This allows you to host a repository on almost any internet service provider without dedicated support.

Work on partial checkout

Whether a user can checkout only a subdirectory of a project and work on it.

Windows support

Whether the Microsoft Windows platform has good native support. Cygwin support is not sufficient.

Fast Local Performance

Whether local operations (commit, "which files have I changed?", diff, switch to different revision, merge) are fast.

Fast Network Performance

Whether network operations (pull, push, clone) are fast.

Details of particular VCSes

In some cases, it is hard to answer 'yes' or 'no' to a particular question.

Bazaar

The current implementation of Bazaar has not excellent network performance for propagating changes (it already has improved much in the switch from weave format to knits format). This is expected to become about 30 times faster in the near future.

Mercurial

Mercurial does not support renames, representing them as copy+delete instead. Its merge doesn't handle renames (support is pending). Other operations such as diff and log also don't follow renames. Since it does not track directories, directory renames are hard for it to represent and remember.

Mercurial supports something called a "repository", but it's not what we mean by repositories: a collection of persistent branches and their revisions. In Mercurial repositories, branches are not persistent: when a merge is committed, the two branches become one.

Mercurial's namespace is complicated because its "named branches" do not have unique urls-- instead, they are a combination of repository URL and a tag name.

The recommended method of branching involves creating a new repository, which is expensive when hardlinks are not available.

Git

Git does not store renames. However, features like merge can make pretty good guesses about renames. Git does not work on native Windows, but does work (slowly) on Cygwin.

Subversion

Subversion does not support decentralized operation, but svk is a decentralized VCS implemented on top of svn. Subversion can also do some things (like comparisons of the working directory against the checked out version) without a connection to the server, but for anything that actually affects the repository (like a checkin), Subversion needs to be able to talk to the server. Subversion records renames as copy + delete.