Gentoo Archives: gentoo-dev

From: Alec Warner <antarus@g.o>
To: Gentoo Dev <gentoo-dev@l.g.o>
Subject: Re: [gentoo-dev] gentoo-x86 and git
Date: Mon, 10 Feb 2014 20:53:29
Message-Id: CAAr7Pr8OY7dUn298t+v+wwkvj3L9GJtu8-PPMGC=+CM-DErRWg@mail.gmail.com
In Reply to: [gentoo-dev] gentoo-x86 and git by Patrick Lauer
1 On Mon, Feb 10, 2014 at 4:33 AM, Patrick Lauer <patrick@g.o> wrote:
2
3 > Ahoi,
4 >
5 > I've been looking for a clean git-converted gentoo-x86 repo for ... well
6 > ... mostly data mining as cvs / anoncvs.g.o is too slow for some things.
7 >
8 > This has been needlessly challenging, which confuses me a bit.
9 >
10 > First, a little complaint:
11 >
12 > There used to be some data at git-exp.overlays.gentoo.org, but that
13 > machine has vanished. Ok, stuff happens, but that's not motivating.
14 >
15 > Anoncvs.g.o is bouncing up and down a lot, so just getting the raw cvs
16 > repo to do a local conversion is somewhere between needlessly hard and
17 > impossible.
18 >
19
20 As I had initially advised, you can rsync the entire CVS repo and do the
21 entire conversion locally using cvs pserver. You don't need to rely on
22 anoncvs. As you have noticed, it doesn't exactly have high marks for
23 uptime. Plus a local conversation is much faster; you don't get the network
24 latency for all the cvs operations.
25
26 -A
27
28
29 >
30 > The gentoo-scm mailinglist has mostly fallen asleep, but even the stuff
31 > discussed there doesn't seem to exist in a public repo that can be found
32 > without telepathy skills.
33 >
34 > So ... well ... if it's that hard to just find out the state of the last
35 > experiments there won't be much contribution.
36 >
37 > There is a git repository at https://bitbucket.org/lmnd/gentoo-x86 - but
38 > (1) it has truncated history and (2) it diverges by >1500 files from
39 > gentoo-x86 for the last week. So that's mostly useless for data mining.
40 > (I haven't tried figuring out how it diverges, but raw ebuild count is
41 > +1600 for "yesterday", so that's baad)
42 >
43 > I'd appreciate it if people that worked on the conversion would point me
44 > at the scripts and documentation they used; I'd appreciate a proper
45 > 'official' repo to collect such things; and it'd be really useful to
46 > have the work-in-progress converted repo online so that people can
47 > experiment with it.
48 >
49 > (If anyone needs webspace or similar for that, well, I run lots of cruft
50 > anyways, so another annoying thing won't matter ...)
51 >
52 > Thanks for your support,
53 >
54 > Patrick
55 >
56 > P.S. If anyone feels an overwhelming urge to point out the irony ...
57 > don't ;)
58 >
59 >