1 |
On Thu, 2008-04-03 at 13:49 +0200, Arfrever Frehtes Taifersar Arahesis |
2 |
wrote: |
3 |
> > > If we used git, proxy maintaining would be easier. |
4 |
> > > |
5 |
> > |
6 |
> > True, but with some acls we could also have a different model where people |
7 |
> > worked on parts of the tree and where commit privileges didn't pose so many |
8 |
> > security risks. With the current practice of doing work in overlays it would |
9 |
> > also be simpler to merge the work back into the Portage tree. |
10 |
> |
11 |
> Also Subversion would be sufficient. |
12 |
|
13 |
Release Engineering has been using subversion for the 2008.0 snapshot |
14 |
tree. The repository is running in tmpfs on a dual Opteron box. IT's |
15 |
still quite painfully slow. Of course, we're doing commits at the |
16 |
top-level since we have a single top-level ChangeLog for the repository, |
17 |
but we don't even have history. We literally just pulled ebuilds from |
18 |
the tree. |
19 |
|
20 |
Once the release is done, we can play around with the repository all |
21 |
that we want to get some real numbers, but unless there's some magic |
22 |
bullet that I'm missing, subversion might simply be too damned slow for |
23 |
our needs. As an anecdotal example, I've had a single commit of several |
24 |
profiles take up to 6 minutes to complete, and that's not with repoman |
25 |
or anything. |
26 |
|
27 |
-- |
28 |
Chris Gianelloni |
29 |
Release Engineering Strategic Lead |
30 |
Games Developer |
31 |
-- |
32 |
gentoo-dev@l.g.o mailing list |