David Holland wrote: > On Sat, Sep 05, 2009 at 11:38:01PM +0200, Jan Danielsson wrote: > > Just to make development and tracking -current somewhat faster/easier > > for people like me. > > This is not what you asked for, but it's fairly straightforward to set > up your own system by checking out a tree and then cloning it (along > with the CVS control files and everything) using your favorite > distributed SCM. Yes, that's how I'm currently doing it. But I thought it would be nice to have all of it [the repository] so I could easily switch to different branches when the need arises (for instance, I want to see how difficult it would be to back-port my patches). But it was the failure to do so which was the reason I suggested TNF do it. :) Unfortunately cvsps aborts with an error (something along the lines of "Broken revision number", somewhere under i386/conf, I believe). I tried bazaar and git, both which can use cvsps for cvs-import. I even, as suggested by some web site, tried to do a two-stage import in case the simple cvs-import import failed, but with the same results. I'm not at all proficient in the internals of CVS, so I can't determine if this is caused by a problem with cvsps or if there really is a problem in the netbsd repository. The reasons I suggested TNF do it is because I bet there are people there who are really proficient in CVS and can work around these kinds of problems without having to learn the internals of CVS first. Also, I find CVS to be slow. My current solution works ok, but I would prefer a solution which isn't only to my own benefit, and I would like to be able to easily switch branches. > This is what I've been doing for some time, and I suspect I'm not the > only one. Have you (or anyone else reading this for that matter) tried to do an import of the entire repository? If so, with which SCM, and with which import method? -- Kind regards, Jan Danielsson
Attachment:
signature.asc
Description: OpenPGP digital signature