Language Selection

English French German Italian Portuguese Spanish

DVCS Round-Up: One System to Rule Them All?--Part 1

Filed under

A recent development in the field of version (or revision) control software is the emergence of distributed systems. These discard the notion of a central repository where all project history is kept, and replace it by a network of several repositories that are synchronised regularly. In this model, a developer has a complete repository on his hard disk, which is synchronised with the “outside” whenever deemed necessary. This way one can commit early and often, without fear of breaking the others' code, and it also reduces network load as it does not need a network connection for every small change. In practise, of course there will be a central repository after all, but this is a decision made by the developers and not dictated by the system.

Working distributed has other advantages, too. For example, backups become a no-brainer, since every developer has the complete project history. The classic dilemma of who should have write access to the main project repository becomes significantly less problematic, since the maintainers simply pull the changes from a few persons they trust, which in turn (hopefully) have done likewise beforehand. Linus Torvalds referred to this as a “network of trust,” which is actually the same principle for any security and encryption software.

So, while distributed version control has several advantages, one problem remains: we have to choose one that (hopefully) fits our needs. At the time of this writing, at least half a dozen systems compete for the developers' affections, and this series will hopefully provide you with a basis for your decision.

In this review, we will take a look at six different revision control systems. Namely these are git, Mercurial, darcs, Monotone, Bazaar (which is used by the Ubuntu project), and SVK (which is based upon Subversion). All six systems are distributed, and we will take a look at the different workflows supported (or enforced) by them.

More Here

More in Tux Machines

today's howtos

The Red Hat Way

  • Red Hat wants to make cold-shouldered OpenStack red hot
    At OpenStack Summit in Boston last May, some speculated that the event might be the last gasp for OpenStack — an open-source platform for cloud computing and infrastructure-as-service. Granted, OpenStack was one of the less hyped open-source projects of the past year. But renewed community and end-user interest is breathing fresh life into the platform, according to Rob Young (pictured), senior manager of virtualization product and strategy at Red Hat Inc. Telcos and others are adopting OpenStack “because of the simplification of what was once complex, but also in the cost savings that can be realized by managing your own cloud within a hybrid cloud environment,” Young said.
  • Improved multimedia support with Pipewire in Fedora 27
    Pipewire — a new project of underlying Linux infrastructure to handle multimedia better — has just been officially launched. The project’s main goal is to improve the handling of both audio and video. Additionally, Pipewire introduces a security model to allow easy interaction with multimedia devices from containerized and sandboxed applications, i.e. Flatpak apps.
  • Architecting the future with abstractions and metadata
    The modern data center is built on abstractions, with Docker, Kubernetes, and OpenShift leading the way.

Games: Racing Games, Steam, SteamWorld Dig 2, XCOM 2: War of the Chosen

Software: DNS Checkers, Alternatives to Adobe Software, Fake Hollywood Hacker Terminal and More