From: "Caleb Tennis" <caleb@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] The deal with epkgmove
Date: Sat, 10 Dec 2005 11:03:49 -0500 (EST) [thread overview]
Message-ID: <62160.69.136.169.173.1134230629.squirrel@www.aei-tech.com> (raw)
In-Reply-To: <20051210145345.GS1198@mail.lieber.org>
> As for moving packages by hand vs. using a tool, that's not really infra's
> call. If you were asking about CVS vs. SVN, I have been and remain
> opposed
> to using SVN for gentoo-x86 until someone can offer a whole lot of
> assurances around SVN's ability to manage a repo of our size. (1.3GB,
> 216,000+ files and counting)
KDE moved to Subversion earlier this year, with a few million lines of
source code and hundreds of branches and tags. It did it flawlessly and
maintained over 400,000 commit history items.
I don't think stability is the biggest hurdle here. I think the
conversion process will be - they had to write a lot of code from scratch
to handle maintaining all of that history (the stock cvs2svn wasn't robust
enough), and they had to run the conversion process a number of times,
find the bugs, rework their conversion code, and rerun. It was a lengthy
process (a few weeks I believe).
It's going to require someone to actually write the conversion code and
provide a proof of concept conversion. If anyone's up to the challenge, I
imagine contacting their sysadmins would be a good start.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-12-10 16:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-10 11:52 [gentoo-dev] The deal with epkgmove Ian Leitch
2005-12-10 14:53 ` Kurt Lieber
2005-12-10 15:56 ` Luca Barbato
2005-12-10 16:51 ` Benoit Boissinot
2005-12-10 17:07 ` Jason Stubbs
2005-12-10 17:19 ` Dan Meltzer
2005-12-10 17:29 ` Ciaran McCreesh
2005-12-10 17:34 ` Fernando J. Pereda
2005-12-10 16:03 ` Caleb Tennis [this message]
2005-12-10 16:04 ` Caleb Tennis
2005-12-12 4:23 ` [gentoo-dev] " R Hill
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=62160.69.136.169.173.1134230629.squirrel@www.aei-tech.com \
--to=caleb@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox