[arch-dev-public] Killing CVS [was: Status Report 2007-10-15]

Aaron Griffin aaronmgriffin at gmail.com
Fri Oct 19 20:06:39 EDT 2007

On 10/17/07, Jason Chu <jason at archlinux.org> wrote:
> I don't care about what Aaron says here.  Whether I disagree or not really
> doesn't matter.  The point he's trying to get to is let's try something
> (without necessarily putting it into place right away) and talk about that
> instead of just talking about the ideas.

Ok, keeping things rolling here. This thread is marked in my little
"to respond" bucket, but I haven't had enough time to get to it.


a) First off, this work is here, and that means quite a lot to me.
Even if I don't think the concept is "perfect", it's done and it's

b) The concepts for the tools are solid. I actually didn't like the
single package checkout at first, but it's grown on me.  For those
that don't get it, here's a usecase:

   cd ~/mypackages
   archco gtkpod
   cd gtkpod && do stuff
   cd ..
   archco fetchmail
   ...etc etc...

This means two things. 1) You don't need the whole repo checked out
all the time, so it saves on disk space, and 2) you can have a nice
subset of packages in a directory, instead of having to hunt for

c) Could you explain how the usage would work with the svnmerge tool.
Personally, it's a little confusing with the repos/ dir, even though I
had a small part in this original idea 8)


This implementation grew on me as archco did. I don't think it'd be as
easy with an other SCM. But I still am a little put off by svn - after
having used fancier SCMs out there, I don't really like the tamer ones
anymore. git has some GREAT tools, but I don't think we'd need half of

I'd still love to see a git or even mercurial implementation (bonus
points: mercurial works on Win32 better, so we could ease into a
'cygwin' arch, which is something I wanted to try out for a while,
When I have time and finish up some things I wanted to finish, I will
see about a git implementation.
I believe Dan already has something, so he may beat me.

Anyone else have something to add?

More information about the arch-dev-public mailing list