Slashdot Mirror


BitMover Releases Open Source BitKeeper Client

diegocgteleline.es writes "Larry McVoy, the owner of BitKeeper (also one of the guys behind LMbench) has posted a message to linux-kernel where he announces a open source client of BitKeeper, which would only allow synching against BK trees. It looks like it's licensed under the NWL (No Whining License) that will force you to 'not whine about this product or any other products from BitMover, Inc.'"

54 of 255 comments (clear)

  1. No Whiners License... by ABeowulfCluster · · Score: 5, Funny

    So.. this doesn't run under WINE then.

    1. Re:No Whiners License... by ozbird · · Score: 2, Funny

      Fair enough, but are sniveling, grizzling, yammering and yawping permitted?

  2. No WINEing? by LewsTherinKinslayer · · Score: 2, Funny

    So.. this doesn't run under WINE then.

    Ba-dum-ching.

    1. Re:No WINEing? by Gulthek · · Score: 2, Funny

      00:00 [cue laughtrack]

      00:03 [cue groans]

  3. Re:Strange by sampowers · · Score: 5, Informative

    Don't be a stupid. At least read the mailing list posting:

    Don't worry about the license, it's a joke. BSD license OK with everyone? /blockquote
  4. Bazaar-NG by Cronopios · · Score: 5, Interesting

    Too late.

    Right know, I put my expectations on Bazaar-NG: all the goodies of GNU Arch and the simple interface of Subversion. Developed by Canonical (of Ubuntu fame).

    --
    Windows users:
    Internet Explorer is obsolete. Please upgrade to Google Chrome or Mozilla Firefox.
    1. Re:Bazaar-NG by Per+Abrahamsen · · Score: 4, Insightful

      The original implementation of GNU Arch was done in bourne shell. Pyhton is a big step up from that.

      In any case, I think it is a fine combination when the core functionality of a program is written in a statically typed language, and UI binding it together is written in a dynamically typed language.

    2. Re:Bazaar-NG by shish · · Score: 4, Insightful
      How do I use bazaar, arch or subversion to check out the kernel's bitkeeper repositories?

      The point of this article is that you no longer need to use the "we own your soul" closed source BK client just to download the kernel; you can use the open source client instead.

      --
      I mod down anyone who says "I will be modded down for this", regardless of the rest of their comment
    3. Re:Bazaar-NG by millette · · Score: 4, Interesting

      Maybe you'd prefer a haskell implementation ? Darcs is decentralized, based on a "theory of patches" with roots in quantum mechanics.

      Written in Haskell, darcs is used on many operating systems including Linux, MacOS X, FreeBSD, and Windows. Darcs includes a CGI script to browse your repository from the web.

    4. Re:Bazaar-NG by cakoose · · Score: 2, Informative

      Dude, read the Bazaar webpage. Just the front page. It's clearly not a fork. They want to have some level of interoperability, but that's about it. They wrote it in Python and have a totally different user interface.

    5. Re:Bazaar-NG by Sweetshark · · Score: 2, Informative

      It is just sad that it's written i Python. I like Python for scripting, but production software should not be written in dynamically typed scripting languages.
      Yeah, we all know scripting languages suffer from buffer overflows and other serious flaws. So sgi, NATO and Viacom and gentoo did it all wrong:
      http://www.zope.org/Resources/ZopePowered/
      http://www.gentoo.org/proj/en/portage/index.xml
      The fact that the use of Python is listed as one of the top features indicates that the programmers behind this project are either immature, untalented, or both.
      For what reason?

  5. Indeed... by Svartalf · · Score: 3, Insightful

    Larry's entitled to license things under any license he wants to. It's HIS product. However, having said this, it's still quite understandable for people to not want Linux development being tied to a closed-source product with nasty gotchas in it's free license. That's not whining in the least.

    The only thing resembling "whining" seems to be coming from Larry himself with this silly license. All it's going to do is make the acrimony WORSE, not better. Kind of childish, in my not so humble opinion.

    --
    I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
    1. Re:Indeed... by RedWizzard · · Score: 2, Insightful
      However, having said this, it's still quite understandable for people to not want Linux development being tied to a closed-source product with nasty gotchas in it's free license. That's not whining in the least.
      Larry's view is that it's whinning because they don't have to use BK and it not using it doesn't put them in a worse position than they were in before BK was adopted. He's kind of got a point there, though it's by no means black and white. Still the "whinning" could have been a lot worse. Just imagine if Linus had of adopted a commercial system (it's not like he's religous about using open-source tools).
      The only thing resembling "whining" seems to be coming from Larry himself with this silly license. All it's going to do is make the acrimony WORSE, not better. Kind of childish, in my not so humble opinion.
      You might have a point, except that license is a joke. It's under the BSD license.
    2. Re:Indeed... by Anonymous Coward · · Score: 5, Insightful

      However, having said this, it's still quite understandable for people to not want Linux development being tied to a closed-source product with nasty gotchas in it's free license. That's not whining in the least.

      The problem is that people who whined about BK being propietary should have shut their mouth up, but they didn't. When Linus switched to BK, he made clear that he would NOT force to anyone to use BK, and that's how it has been: Linux kernel.org releases are released in GNU diff format, so everybody can code and contribute. The one reason why all^Wmost of the kernel developers use BK is because they aren't stupid, BK is a great tool and can save hours of work, and it lets them to work easier between those who use BK. When someone wants to get a patch to get merged they also made the GNU diff format patch available, and even if they didn't, bkbits.net provides you a link to get a GNU diff patch for every changeset out there. Those who claim that "anyone who wants to closely track patches to Linux can only do it by installing that non-free program" to develop the kernel are just wrong because you have access to the latest kernel changes without installing a non-free tool. -mm and -ac tree are maintained using open tools, so I don't see where is BK being "required".

      The one reason why people whine is because they want to have the advantages of BK, but without using a propietary tool. That's not possible, there's not a OSS tool comparable to BK, subversion arch and friends are not even close. Everybody agrees that having such tool would be great (Linus even tried to convince Larry to release BK under a open license) but there's not one.

      IMHO is just like when RMS had to use propietary tools to start developing GNU - Linux developers just use BK because using a OSS SCM would mean the linux kernel development would slow down a lot, and that's not good (and again, if you are going to propose to use subversion, arch, etc, it probably means that you do not understand the frenetic kernel development needs and the power of BK)

  6. Re:Strange by tupshin · · Score: 5, Insightful

    Actually he said in the email that the whining license was a joke and he's actually licensing it as BSD (and later said it could even be considered public domain), though until the source code is re-released with proper license headers, I doubt his statement to lkml is legally binding in any way.

    -Tupshin

  7. NWL (No Whining License) by MatthewNewberg · · Score: 5, Funny

    I wonder if someone could extend said license to other things in life such as Family, Jobs and Girlfriends..

    1. Re:NWL (No Whining License) by Anonymous Coward · · Score: 2, Funny

      I wonder if someone could extend said license to other things in life such as Family, Jobs and Girlfriends...

      What are these "Jobs and Girlfriends" things of which you speak?

  8. Re:Strange by Chasuk · · Score: 4, Interesting

    I don't know how relevant this is, not quite getting the gist of the article, but does this sentence (linked from the word message in the article) make any difference? Or was I not supposed to follow any of the links?

    Don't worry about the license, it's a joke. BSD license OK with everyone?

  9. Open alternatives by ballermann · · Score: 5, Interesting

    There are so much real open alternatives like subversion, arch and (my personal favourite) darcs - just to name a few. Why bother with bitkeeper?

    --

    Need a Wiki? Check out DokuWiki

    1. Re:Open alternatives by Chris_Mir · · Score: 5, Funny

      Whoa cool. You should talk to Linus! I'll bet he didn't look into those yet!

    2. Re:Open alternatives by Anonymous Coward · · Score: 2, Insightful

      You never saw any problem in a one-user project.
      Unfortunately you can't just multiply "zero problems times ten thousand users" and end up with 0.

      - Peder

    3. Re:Open alternatives by koko775 · · Score: 3, Insightful

      Because BitMover will itself be a "real open alternative". Why bother with subversion, arch, and (your personal favorite) darcs? Surely it's because you have the power of choice, and the freedom of source?

    4. Re:Open alternatives by winchester · · Score: 4, Insightful
      There are so much real open alternatives like subversion, arch and (my personal favourite) darcs - just to name a few. Why bother with bitkeeper?

      Gosh, get a clue, will you! Or read the lkml archives. Linus chose bitkeeper precisely because all the alternatives you mention don't cut it.

      This is exactlythe attitude that keeps holding open source back. It's not about whether the source is open or not, it is about choosing the right tool for the right job. More people should understand this...

    5. Re:Open alternatives by AuMatar · · Score: 4, Insightful

      No, your attitude is the one with the problem. No current open source solution adequate? Then help make one that is- either by improving an existing alternative, or starting your own. If you don't have the skills/time to do so, encourage others who do to take it up. Just criticizing without doing anything about it helps noone.

      --
      I still have more fans than freaks. WTF is wrong with you people?
    6. Re:Open alternatives by ebyrob · · Score: 2, Insightful

      Gosh, get a clue, will you! Or read the lkml archives. Linus chose bitkeeper precisely because all the alternatives you mention don't cut it.

      Ya, somewhat smaller projects than the Linux kernel like Apache, Mozilla, the GCC and Debian just can't get off the ground since they don't use BitKeeper. Maybe if they switched they'd have better luck...

      I mean really, it's Mr. Torvald's perogative to choose a source control tool he likes and sure when you're on someone else's court you play by their rules. But that hardly makes BitKeeper the holy grail of all source control tools.

    7. Re:Open alternatives by evvk · · Score: 3, Informative

      It is only a client restricted in features.

    8. Re:Open alternatives by slavemowgli · · Score: 4, Informative

      Linus made that choice two years ago, though, and both Arch and Subversion have probably improved since then (I can't talk about darcs, since I don't know that really).

      That being said, it's not just about closed source, although that certainly is a factor, too (did you ever think about where those GNU tools you're (probably) using on a daily basis came from, and why they were created?); the problem with BK is not so much that it's closed-source, but that its "free" (as in beer) license does not permit you to work on any projects that could be seen as competing. That's a serious restriction of your own freedom, and it sure does overstep some ethical boundaries at least because it not only tells you what you can and cannot do with the software in question (BK), but also what you can and cannot do in the rest of your life. There is at least one kernel developer I can remember right now (Andrea Arcangeli) who got bitten by this - he already worked on Arch (I think - it may have been another system, too, though) in the past, so he simply could not use BK at all, and until now, he could not even directly access Linus' BK tree, instead having to rely on things like the bk2cvs gateway etc.

      And what's also bad about the whole thing is that this is not the deal that was initially promised: initially, it was (basically) "you (the kernel developers) get to use our commercial product (BK) for free, and we get the opportunity to use the fact that you use it to advertise BK and show how it's able to efficiently handle even large projects". I can definitely understand why Andrea (and others) were upset, and while Linus had to take many things into account (and while it certainly is clear that BK did provide a substantial improvement over CVS), I think the criticism of BK is all but unjustified (and Larry's arrogant and condescending attitude which he showed in many, many lkml posts didn't exactly help, either).

      --
      quidquid latine dictum sit altum videtur.
  10. Re:Strange by M1FCJ · · Score: 3, Insightful

    Thinking of his track record, I wouldn't bet on his software. First you couldn't do anything, then you couldn't even use it if you were messing with other source control systems, now he is saying it is free for anything. If someone reverse engineers a GPL/BSDL BitKeeper server clone using the client will he tolerate it or will he try to crush it? That's the crux of it.

  11. FTFA... by FireballX301 · · Score: 5, Informative

    Don't worry about the license, it's a joke. BSD license OK with everyone?

    1. Re:FTFA... by stor · · Score: 2, Insightful

      Argh. Yes I should have RTFA and not posted somehting so inflammatory.

      I actually meant it in the nicest possible way ;)

      I like reading LKML and I like Larry and appreciate his gift but he seems to get sucked into the relentless BK flamewars and catalyse them sometimes which I think is unfortunate. He'd do himself a great service avoiding getting too involved imnsho.

      I guess I didn't help just then. Ahh well. Sorry Larry et al.

      Cheers
      Stor

      --
      "Yeah well there's a lot of stuff that should be, but isn't"
  12. Re:Strange by Gordonjcp · · Score: 4, Funny
    Or was I not supposed to follow any of the links?


    You ain't from round here, are ya, boy?

  13. Bitkeeper website by kihjin · · Score: 5, Informative

    "BitKeeper has made me more than twice as productive, and its fundamentally distributed nature allows me to work the way I prefer to work - with many different groups working independently, yet allowing for easy merging between them."
    -- Linus Torvalds, February 2004

    Linus did it. I can too! *jumps on the bandwagon*

    --
    This slashdot-related signature is a stub. You can help kihjin by expanding it.
    1. Re:Bitkeeper website by greppling · · Score: 3, Interesting
      This has been quoted so many times, I still think it is a silly exaggeration. A couple of things changed when Linus switched to BK:

      1. He wrote scripts so that he didn't have to jump between applying patches and reading e-mail, instead he is now reading a batch of patches, queuing them, and then starts a script to apply them.
      2. Developers have instant access to Linus' tree. Any source control system would have provided this.
      3. The comments to the patches in the e-mails sent to Linus now actually make it to the public. Just about any GNU project does this via ChangeLog under any revision control system.
      4. A script was written to automatically extract release notes from the changelog comments.
      5. Merging with subsystems maintainer is easier if they pile up the patches in bitkeeper repositories.

      Maybe all of the above together yielded a factor of two. But only with respect to 5. is BK at all relevant. And even there -- by a HUGE amount the largest merge point is Andrew Morton, who uses quilt instead of BK to manage his tree with some hundred patches per week throughput to Linus. And I haven't read any complaints from Linus that he isn't using BK.

  14. No whining? Weak! by shadowmatter · · Score: 5, Funny

    They should have used the Open Profanity License instead!

    - shadowmatter

  15. I wonder how this bitkeeper thing compares by melted · · Score: 4, Interesting

    I wonder how this bitkeeper thing compares to the state of the art, Perforce. Perforce charges $700 per seat, and after working with it for years, I can say it's worth it. Everything is just the way it should be. I wish someone would reimplement the damn thing under GPL license. After using Perforce at work, all other systems look like a joke.

    1. Re:I wonder how this bitkeeper thing compares by leshert · · Score: 2, Insightful

      To quote The Princess Bride, "I do not think it means what you think it means."

      "State of the art" doesn't mean "best overall implementation". It means that it implements the most recent advances in the field. Perforce is actually quite conventional (being originally based on either RCS or SCCS--I can't recall which). It uses the "single authoritative repository" model of version control.

      The "state of the art" in version control is exploring the model of distributed and decentralized repositories. BK, darcs, arch, etc. are implementations of this model.

      That being said, I like Perforce--a lot. In fact, just this year I helped successfully push for its adoption at work (beating out StarTeam and ClearCase). Perforce is fast, reliable, and not exceedingly complex for end users.

      I'm not yet convinced that the distributed repository model is the best model for all purposes, but it's certainly closer to the usual meaning of "state of the art" than Perforce.

    2. Re:I wonder how this bitkeeper thing compares by Anonymous Coward · · Score: 5, Informative
      It compares much better than perforce.

      With Bitkeeper it's very easy for every organization - and even every developer - to have his own "fork" of the tree which acts as a "master repository" for others to create branches off of.

      For example, within RedHat, they can have one (or many) child branches from Linus's branch (or any other developer's branches); and "reparent" the branches as needed to merge in the various pieces they need. Other employes' repositories may point to one inside RedHat; or they may point to Linus's; and of course they can "reparent" their repository to switch between the two as needed.

      Similarly, any company or group of developers can have similar structures.

      Also; it's important to note that not everyone needs access to a "master repository"; and that indeed no-one needs access to a "master repository" except when they're merging with that master.

      Bitkeeper works perfectly on my laptop in disconnected mode - and I have the full power of the source control system on my laptop even with no net access - I can create branches, merge branches, etc. If I'm traveling with someone else from the company I can merge my branches with his merely with a cable between the laptops - no connection to the home office is needed.


      We used perforce at a previous company I was at with offices in China, Taiwan,Romania, and California and it was a horrible experience. Connecting to oversees repositories was painful; and merging changes between the oversees repositories sucked even worse.

      Try BitKeeper. I'm sure you'll switch.

    3. Re:I wonder how this bitkeeper thing compares by Daniel+Phillips · · Score: 2, Interesting

      For example, within RedHat, they can have one (or many) child branches from Linus's branch (or any other developer's branches); and "reparent" the branches as needed to merge in the various pieces they need. Other employes' repositories may point to one inside RedHat; or they may point to Linus's; and of course they can "reparent" their repository to switch between the two as needed.

      How would you know, Mr. Anonymous Coward? The fact is, very few employees at Red Hat use Bitkeeper at all. I should know, I work there. Of the handful that do use BitKeeper, most are maintainers for whom BitKeeper is the route of least resistance. They would all probably switch if Linus switched. The vast majority of Red Hat developers do not use BitKeeper and would violently object to using BitKeeper on any project. This is because of the silly license, and because of a rather natural distrust of closed source tools in the open source toolchain, which BitMover has done their level best to confirm.

      By the way, it's Red Hat, not RedHat.

      --
      Have you got your LWN subscription yet?
  16. Re:Perforce Licensing by hashinclude · · Score: 4, Informative
    Yeah, I love perforce too. The good thing is (if you RTF Licensing terms from the website) is that GPL/BSD and other open source projects can get a P4 license for free.

    Blockquoth the site:

    Organizations developing software that is licensed or otherwise distributed exclusively under an Open Source license may be eligible to obtain Perforce licenses gratis. This includes upgrades but not support. Perforce Software reserves the right to approve the Open Source license; those fitting The Open Source Definition, including the GNU and FreeBSD licenses, are good candidates. Execution of a End User License Agreement for Open Source Software Development (PDF) is required. For more information, please see the Perforce and Open Source FAQ or contact opensource [at] perforce [dot] com
    --
    US is now divided as the "Red" and "blue" states. Red States = communist countries. Coincidence? I think not
  17. Which is nice... by Kjella · · Score: 5, Insightful

    No, your attitude is the one with the problem. No current open source solution adequate? Then help make one that is- either by improving an existing alternative, or starting your own.

    ...if you're trying to do the community a service. If you're looking to put food on the table doing something completely unrelated (where this is simply a support function), it is mindnumbingly stupid. Most likely you're long out of business by the time it is working.

    Sure, if all you need is some minor customization, maybe. But if it clearly isn't anywhere near being up to the task, pick something non-OSS. Earn some money, help out the projects where it is feasible to replace proprietary with OSS.

    That is the way OSS projects prospers. I make a 98% solution a 100% one. That makes it a 98% solution for someone else, who'll make it a 100% solution for them. And the snowball is rolling. Not by one company breaking its back trying to bring it from 40% to 100%.

    Kjella

    --
    Live today, because you never know what tomorrow brings
  18. Presentation about BitKeeper by irabinovitch · · Score: 5, Informative

    Larry McVoy, BitMover Founder, gave a great talk about BitKeeper and the delta development model at SCALE 3x (Southern California Linux Expo) last month. Its available online here. -Ilan

  19. Re:bitkeeper is not on my radar by dave420 · · Score: 3, Insightful
    But you keep your beer in your own fridge, which you don't have the schematics for, so your analogy is somewhat lacking ;)

    I admire your ideology-before-productivity attitude, though... inspiring.

  20. NWL by kspiteri · · Score: 2, Informative

    A copy of NWL can be found at http://lkml.org/lkml/2003/12/14/47/:

    /*
    * tarball.c copyright (c) 2003 BitMover, Inc.
    *
    * Licensed under the NWL - No Whining License.
    *
    * You may use this, modify this, redistribute this provided you agree:
    * - not to whine about this product or any other products from BitMover, Inc.
    * - that there is no warranty of any kind.
    * - retain this copyright in full.
    */

  21. Rule of Thumb by R.Caley · · Score: 2, Insightful
    Always worry about a company who won't give any idea about pricing unless you get in contact with a salesdroid.

    So far as I can see on their website, BitMover fall under that heading.

    --
    _O_
    .|<
    The named which can be named is not the true named
    1. Re:Rule of Thumb by base3 · · Score: 3, Insightful
      The conversation, simplified, is something like this:

      Customer: How much is it?

      Salesman: How much do you have?

      --
      One CPU cycle wasted on digital restrictions management is ONE TOO MANY.
  22. You got the schematics to your fridge by SmallFurryCreature · · Score: 2, Insightful
    It is the fridge itself. From looking at a fridge any skilled craftsman can use it is as a blueprint/schematic to build another.

    This is true for most real world objects. Only software is radically different.

    You can also hack your own fridge all you want without dmca style rules coming into play.

    So his anology works for a skilled craftsman anyway.

    --

    MMO Quests are like orgasms:

    You may solo them, I prefer them in a group.

  23. Re:Any SCCS based replacements with repositories? by bheading · · Score: 2, Informative

    BK isn't actually SCCS based, but it looks like SCCS to external programs which allows make, emacs, patch etc to work seamlessly. It certainly resembles SCCS in the way it manages deltas between versions however.

    The Changeset idea is very nice and you can do a lot of cool stuff. eg if someone integrates a bugfix and your manager decides at the last minute that it shouldn't go in, you can generate an anti-changeset which reverses it. Then you can generate an anti-anti-changeset to reintegrate it. I'd like to see someone trying that on Perforce on a change with 100 files inside.

  24. Re:Perforce Licensing by p3d0 · · Score: 2, Funny

    What if that GPL/BSD project is a replacement for Perforce?

    --
    Patrick Doyle
    I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
  25. This would never be approved by OSI by Russ+Nelson · · Score: 2, Insightful

    This license would never be approved for the "Open Source" logo by OSI. If necessary, I would suggest that we change the OSD to make sure that a license does not impose restrictions on freedom of speech. Sheesh.
    -russ

    --
    Don't piss off The Angry Economist
    1. Re:This would never be approved by OSI by Brandybuck · · Score: 2, Insightful

      The purpose of the license isn't to get OSI approval, but to wag appendages at uptight licensing legalists.

      --
      Don't blame me, I didn't vote for either of them!
  26. Unfair characterization by FreeUser · · Score: 2, Insightful

    I admire your ideology-before-productivity attitude, though... inspiring.

    That is a very unfair (and inaccurate) characterization of the grandparent post.

    Productivity is only one factor, and often not the most critical one. Just as any liability lawyer, security consultant, or sysadmin whose had to recover using an offsite backup.

    Your data is your most valuable possession. The cost (in time, energy, money, resources, you name it) of creating your data far outweighs the value of the hardware it resides on, the software you paid for, and probably even the office in which it resides. It is the one thing insurance can't replace, and the one thing you (or your business) probably can't live without.

    Having your data (e.g. the Linux kernel) beholden to a proprietary product, managed in a proprietary format, is over the long term quite foolhardy. Imagine, for example, if Microsoft were to buy Bitkeeper (this is hardly unimaginable, and arguably not so unlikely). It isn't an "end of the world" scenerio by any means, but it is damn inconvinient to move the kernel sources to another revision control system, and unfortunately for the kernel developers, there is unlikely to be a libre one that suits their purposes available because they haven't been contributing feedback, criticisms, and suggestions for improvement to any of the free projects by virtue of the fact that they aren't using any of them and so aren't in a position to make said suggestions, etc.

    It is generally a mistake to have one's data beholden to a proprietary product. Sometimes it can't be avoided, and sometimes the cost is worthwhile. And sometimes, the results are absolutely catastrophic. Unfortunately, in the case of the Linux kernel, if the results should be catastrophic in some manner, it will be catastrophci for the millions upon millions of Linux users around the world. OTOH there are enough tarballs and parallel CVS repositories around that such a scenerio is very unlikely. What isn't so unlikely is the "OMFG this is painful, we'll have to move to $free-rcs and its going to cost us at least a couple of months productivity."

    Now, in the case of the Kernel, Linus has judged these risks to be small enough, and his productivity improvements to be great enough, for the potential tradeoff to be worthwhile. The grandparent post has judged the opposite. Both may be correct for their respective problem domains, but to characterize the one as "ideology-before-productivity" is very disingenuous, and ignores a whole slew of real-world issues that proprietary management schemes, formats, and restrictions bring to the table.

    --
    The Future of Human Evolution: Autonomy
  27. Re:BitKeeper compared to Darcs. by dozer · · Score: 2, Insightful

    How about full disclosure? Darcs is also really slow, an absolute pig with memory (pretty much requires 1G even for small trees) and falls over on projects even half the size of the Linux kernel. It's a a very good start, but Darcs has a long way to go before it is useful in the real world.

  28. Re:Going too far by Brandybuck · · Score: 2, Insightful

    Actually I am a libertarian, but like everyone else, I do have to live in the real world. Actions have consequences. If you stick your hand in a running garbage disposal, you'll pull out a stump. If you use Michael Jackson as a babysitter, you child will get buggered. If you incessantly whine about your right to incessantly whine, someone's going to beat the crap out of you.

    As a liberatarian, it won't be me who will be pounding your face into a pulp, but as someone who has to live in the real world, don't expect me to be standing at the head of the line to come to your defense.

    Yes, you have the right to be annoying. No, you don't have the right to prevent other people from getting annoyed.

    --
    Don't blame me, I didn't vote for either of them!
  29. OSS software configuration management tools - refs by dwheeler · · Score: 2, Informative
    For some info on OSS configuration management tools, including references to many of them, see Comments on OSS/FS Software Configuration Management (SCM) Systems. That paper, in turn, references lots of other pages on the topic:
    "The better SCM initiative was established to encourage improved OSS/FS SCM systems, by discussing and comparing them. Among other things, see their comparison file. Zooko has written a short review of OSS/FS SCM tools. Shlomi Fish's OnLamp.com article compares various CM systems as does his Evolution of a Revision Control User. The arch folks have developed a comparison of arch with Subversion and CVS (obviously, they like arch). Another pro-arch discussion is Why the Future is Distributed. A pro-subversion discussion is available at Dispelling Subversion FUD. Slashdot had a discussion when Subversion 1.0 was announced. Kernel traffic posted a summary of a technical discussion about BitKeeper. Brad Appleton has collected lots of interesting SCM links. jemfinch has some interesting essays about SCMs (he uses the term VCS), including why he thinks the approach to branches used by Darcs, Arch, and Bazaar-ng is a poor one. A brief overview of SCM systems that can run on Linux is available."

    There are lots of OSS/FS software configuration management (SCM) tools. CVS, Subversion (SVN), and GNU arch get lots of press, but there are many others such as Aegis, CVSNT, Darcs, FastCST, OpenCM, Vesta, Codeville, Bazaar and Bazaar-NG.

    You might also take a peek at my paper Software Configuration Management (SCM) Security.

    --
    - David A. Wheeler (see my Secure Programming HOWTO)