1 |
Sven Vermeulen wrote: |
2 |
> I wouldn't mind to move over to SVN personally. Just Another Versioning |
3 |
> Tool. But I do hope that SVN (don't know it really) supports: |
4 |
|
5 |
Okay, resurrecting the old thread :) |
6 |
|
7 |
> - Running a tool right before the check-in is made permanent (in this case, |
8 |
> check for GuideXML syntax, but in future might be expanded) |
9 |
|
10 |
Yes, SVN supports hooks. |
11 |
|
12 |
> - Annotate function |
13 |
|
14 |
Yup, `svn annotate some/file` (and with a really nice alias `svn blame |
15 |
some/file`). |
16 |
|
17 |
Another benefits: |
18 |
|
19 |
* generating diffs against latest version without contacting the server |
20 |
(SVN creates a pristine copy on a checkout) |
21 |
* possibility to stick arbitrary metadata to files (so the translators |
22 |
could just create a new "property", "en-revision", for example, and use |
23 |
it for keeping track of the version the current translation is based on) |
24 |
* branching, see below |
25 |
|
26 |
Mike Frysinger wrote: |
27 |
> although moving around in cvs is a pita, i dont see it being all that |
28 |
> common in the xml subdir ... many of the other benefits that svn has |
29 |
> over cvs (branching and changesets) just isnt that useful in terms of |
30 |
> website management imo ... |
31 |
|
32 |
Well, just have a look at the draft/ subdirectories, especially those |
33 |
related to the handbooks. |
34 |
|
35 |
|
36 |
Just to be clear - I don't propose the conversion now, during the |
37 |
release work, but I certainly see the benefits that are worth the |
38 |
conversion at a less-exposed time. |
39 |
|
40 |
So, what about a gentoo-doc or gentoo-website repo? Looking at the |
41 |
current structure, GDP/website is interested only in |
42 |
gentoo/cvs/gentoo/xml/, and the "work" subdirectory can be nuked (the |
43 |
only doc is an outdated draft from peitolm). |
44 |
|
45 |
Cheers, |
46 |
-jkt |
47 |
|
48 |
-- |
49 |
cd /local/pub && more beer > /dev/mouth |