[crossfire] CVS -> SVN conversion

[Alex Schultz]

Mark Wedel wrote:
>   Another question for everyone:
>
>   It has been commented/asked several times in the past whether the 
> automatically generated files should be in the repository, or if it should be up 
> to the developer to rebuild them.  There are several types of files, and my 
> general thoughts:
>
> <snip>
Seems like good ideas to me.

>   The only thing which I'm not sure if there is any way to do is have some file, 
> ideally automatically created, that sits in the arch tree so that the server can 
> know that the archs have changed and it should do a collect.  One can manually 
> run the command now, and there is a hidden timestamp file, but that file doesn't 
> do any good if it never changes.
>   
I don't think there's a way to automatically update such a file, unless
we could get special permission from sf.net to use a custom serverside
hook, however I doubt they would allow it. However, if we store the arch
tree and server tree with separate "ttb" as mentioned in Christian
Hujer's mail, we might be able to use svn revision numbers to determine
if it's been updated.

>   As a note, for any files that we automatically generate that are not normally 
> in SVN (if we so decide) yet are in the distributions we ship out, I'd expect 
> they would be in the release branch of the SVN repository for that release (so 
> you can go to the 1.10 branch and see what the archetypes file had, or see what 
> the makefile looked like, etc).  Although, maybe even that is useless - could 
> always just download the old releases.
Seems like a good idea. As noted by Nicolas it would probably be nice to
automate that process to some degree as well.

Alex Schultz