<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
    <title>weblog.masukomi.org - darcs</title>
    <subtitle>Autistic, ADHD, Geek. The weblog of Kay Rhodes (masukomi).</subtitle>
    <link rel="self" type="application/atom+xml" href="https://weblog.masukomi.org/tags/darcs/atom.xml"/>
    <link rel="alternate" type="text/html" href="https://weblog.masukomi.org"/>
    <generator uri="https://www.getzola.org/">Zola</generator>
    <updated>2008-03-11T00:00:00+00:00</updated>
    <id>https://weblog.masukomi.org/tags/darcs/atom.xml</id>
    <entry xml:lang="en">
        <title>Sharing a public Darcs repo over HTTP [flow chart]</title>
        <published>2008-03-11T00:00:00+00:00</published>
        <updated>2008-03-11T00:00:00+00:00</updated>
        
        <author>
          <name>Kay Rhodes</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://weblog.masukomi.org/2008/03/11/sharing-a-public-darcs-repo-over-http-flow-chart/"/>
        <id>https://weblog.masukomi.org/2008/03/11/sharing-a-public-darcs-repo-over-http-flow-chart/</id>
        
        <content type="html" xml:base="https://weblog.masukomi.org/2008/03/11/sharing-a-public-darcs-repo-over-http-flow-chart/">&lt;p&gt;&lt;img src=&quot;http://s3.amazonaws.com/mobtvse_masukomi/assets/2008/03/config_remote_darcs_repo.jpg&quot; alt=&quot;sharing a public Darcs repo overhttp&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; /&gt;
The same friend who wondered about &lt;a rel=&quot;external&quot; href=&quot;https://weblog.masukomi.org/2008/03/11/sharing-a-public-git-repo-over-http-flow-chart&quot;&gt;how to share a Git repo over
HTTP&lt;/a&gt; dared to suggest that “It’s so easy with Hg…”. While I happen to
disagree that it’s easier in &lt;a rel=&quot;external&quot; href=&quot;http://www.selenic.com/mercurial/&quot;&gt;Hg&lt;/a&gt;
than &lt;a rel=&quot;external&quot; href=&quot;http://git.or.cz&quot;&gt;Git&lt;/a&gt;, I think this flow chart successfully
demonstrates that, on this front, Hg and Git both suck ass when compared
to &lt;a rel=&quot;external&quot; href=&quot;http://darcs.net/&quot;&gt;Darcs&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;P.S. Yes, while 100% factual, the graph is also intentionally silly.&lt;/p&gt;
&lt;p&gt;[Update] After considering it more I think think it probably is easier
to share a repo with Hg than Git, but I dislike the fact that it
involves mucking about with things outside of the repo. You have to set
up a CGI. You have to alter a config file that tells it what repos to
share and where…. Yes, there’s a built in server you could use but
that’s really an edge case. Most of the time you’ll want to leverage an
existing web server.&lt;/p&gt;
</content>
        
    </entry>
    <entry xml:lang="en">
        <title>Using Darcs with SVN / CVS Flow Chart</title>
        <published>2007-05-23T00:00:00+00:00</published>
        <updated>2007-05-23T00:00:00+00:00</updated>
        
        <author>
          <name>Kay Rhodes</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://weblog.masukomi.org/2007/05/23/using-darcs-with-svn-cvs-flow-chart/"/>
        <id>https://weblog.masukomi.org/2007/05/23/using-darcs-with-svn-cvs-flow-chart/</id>
        
        <content type="html" xml:base="https://weblog.masukomi.org/2007/05/23/using-darcs-with-svn-cvs-flow-chart/">&lt;p&gt;A flow chart for a friend demonstrating, step by step, how you’d go
about using &lt;a rel=&quot;external&quot; href=&quot;http://www.darcs.net&quot;&gt;Darcs&lt;/a&gt; (or any other distributed
version control system) with SVN / CVS. He needs to do it for the most
common reasons:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;it’s a pain to branch and merge with CVS.\&lt;/li&gt;
&lt;li&gt;he’d have to coordinate with other departments like QA to get them
working off of whatever the current release branch happened to be at the
moment and convince them that it was a good idea.&lt;/li&gt;
&lt;li&gt;currently his co., like so many, is working off of a single
development trunk. There are no other branches.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Click on the image to get a full sized version. Or &lt;a rel=&quot;external&quot; title=&quot;download the dia file here&quot; href=&quot;http://s3.amazonaws.com/mobtvse_masukomi/assets/2007/5/23/using_darcs_with_svn.dia&quot;&gt;download the dia
file
here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a rel=&quot;external&quot; href=&quot;http://s3.amazonaws.com/mobtvse_masukomi/assets/2007/5/23/using_darcs_with_svn.png&quot;&gt;&lt;img src=&quot;http://s3.amazonaws.com/mobtvse_masukomi/assets/2007/5/23/using_darcs_with_svn_small.png&quot; alt=&quot;image&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; /&gt;&lt;/a&gt;&lt;br /&gt;
&lt;a rel=&quot;external&quot; href=&quot;http://creativecommons.org/licenses/by-sa/3.0/us/&quot;&gt;&lt;img src=&quot;http://i.creativecommons.org/l/by-sa/3.0/us/88x31.png&quot; alt=&quot;Creative CommonsLicense&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; /&gt;&lt;/a&gt;&lt;br /&gt;
This work is licensed under a &lt;a rel=&quot;external&quot; href=&quot;http://creativecommons.org/licenses/by-sa/3.0/us/&quot;&gt;Creative Commons Attribution-Share Alike
3.0 United States
License&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Some earlier related posts:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a rel=&quot;external&quot; title=&quot;Why you should be using a distributed source control system&quot; href=&quot;https://weblog.masukomi.org/2006/12/29/distributed-scm&quot;&gt;Why you should be using a distributed source control
system&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a rel=&quot;external&quot; title=&quot;Using Darcs with Subversion / CVS&quot; href=&quot;https://weblog.masukomi.org/2007/3/29/using-darcs-with-subversion-cvs&quot;&gt;Using Darcs with Subversion /
CVS&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a rel=&quot;external&quot; href=&quot;https://weblog.masukomi.org/2006/12/29/distributed-scm&quot;&gt;Why you should be using a distributed source control
system&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
        
    </entry>
    <entry xml:lang="en">
        <title>Using Darcs WITH Subversion / CVS</title>
        <published>2007-03-30T00:00:00+00:00</published>
        <updated>2007-03-30T00:00:00+00:00</updated>
        
        <author>
          <name>Kay Rhodes</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://weblog.masukomi.org/2007/03/29/using-darcs-with-subversion-cvs/"/>
        <id>https://weblog.masukomi.org/2007/03/29/using-darcs-with-subversion-cvs/</id>
        
        <content type="html" xml:base="https://weblog.masukomi.org/2007/03/29/using-darcs-with-subversion-cvs/">&lt;h2 id=&quot;using-darcs-with-subversion-cvs&quot;&gt;Using Darcs with Subversion / CVS&lt;/h2&gt;
&lt;p&gt;Some of you have gotten the distributed version control religion (If
you haven’t, you should read my &lt;a rel=&quot;external&quot; title=&quot;Best Practices essay&quot; href=&quot;http://www.masukomi.org/writings/best_practices/&quot;&gt;Best Practices
essay&lt;/a&gt;)
but are stuck with Subversion (or CVS) either because that’s what they
use at work or because some part of your deployment systems use it. You
may also want to combine them simply because of the power of svn
externals which lets you pull in some of your code from constantly
updated , Subversion Based, 3rd party repositories. Using SVN with a
distributed version control system also gets you a cannonical, no doubt
about it, central repo, instead of just a repo that everyone agrees to
call the central one, plus you can utilize all those nifty notification
and stats tools people have written for svn.&lt;/p&gt;
&lt;p&gt;What makes this work so easily is the fact that Darcs stores everything
in one _darcs directory instead of the SVN / CVS approach of throwing
files in every single directory. There are a ton of reasons to use Darcs
(or it’s competitors) when working in a corporate env (even one that
uses SVN / CVS) but my favorite is that you get the full benefit of
version control on all your work and can check in all the buggy crappy
unfinished code you want without polluting the central repo that affects
other developers (until you want to). It’s my practices to do a checkin
when I leave work every day, no matter if I’m finished with what I was
working on or not. With Darcs it doesn’t matter, because I won’t break
anyone elses unit tests because it’s just my personal version control
system that’s effected. When I’m done with whatever I was working on and
it passes all the tests I can push it back out to other developers.
Along the way I’ve been able to make as many revisions of the files as I
wanted to without screwing anyone else over.&lt;/p&gt;
&lt;h3 id=&quot;sneaking-darcs-in-under-the-radar&quot;&gt;Sneaking darcs in under the radar:&lt;/h3&gt;
&lt;p&gt;For those of you who have to use Subversion / CVS at work sneaking Darcs
in for your personal benefit it trivial. Just follow these steps for
each branch (in svn / cvs ) that you need to work on.&lt;/p&gt;
&lt;p&gt;check out a copy of the branch / trunk / tag / whatever that you’ll have
to coordinate with others.&lt;/p&gt;
&lt;p&gt;assuming you want to version control everything that got checked out
you’d cd into that directory and&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;darcs add -r *&lt;/li&gt;
&lt;li&gt;darcs record -am “Initial Import from svn version XXX”&lt;/li&gt;
&lt;li&gt;Don’t worry. Darcs is smart enough to ignore all of your subversion
files.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;From now on whenever you want to start working on something for this
branch you just move to wherever you want to checkout a new repo for a
feature spike / bug fix / whatever and do a “darcs get”&lt;/p&gt;
&lt;p&gt;Use Darcs as you normally would, checking in whenever you want without
worry.&lt;/p&gt;
&lt;p&gt;When you’re done with your feature spike / bug fix / whatever do a
“darcs push” back into the dir where you started, then cd to that
directory and do a “ svn commit -m “some comment here” “ (remember you
haven’t added the _darcs dir to svn so you don’t have to worry about it
getting checked in).&lt;/p&gt;
&lt;p&gt;Snicker in the knowledge that you’ve beaten “The Man”.&lt;/p&gt;
&lt;h3 id=&quot;combining-forces-for-everyone&quot;&gt;Combining forces for everyone:&lt;/h3&gt;
&lt;p&gt;So you’ve convinced everyone to use Darcs. Yay, but for whatever reason
you’ve decided to keep SVN. Just follow steps 1-5 above. You could
theoretically check in your _darcs dir but I suspect that might just
lead to more headaches than it’s worth, especially when you consider how
easy it is to create a new darcs repo (steps 2.1-2.2) and the fact that
you only have to do this the first time you check something out, which
is to say, almost never.&lt;/p&gt;
&lt;p&gt;If you’ve tried checking your _darcs dir into svn please add a comment
so that I, and others, can learn from your experience.&lt;/p&gt;
&lt;p&gt;[Update] Related posts:&lt;br /&gt;
&lt;a rel=&quot;external&quot; href=&quot;https://weblog.masukomi.org/2007/5/23/using-darcs-with-svn-cvs-flow-chart&quot;&gt;Using Darcs with SVN / CVS Flow
Chart&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a rel=&quot;external&quot; href=&quot;https://weblog.masukomi.org/2006/12/29/distributed-scm&quot;&gt;Why you should be using a distributed source control
system&lt;/a&gt;&lt;/p&gt;
</content>
        
    </entry>
</feed>
