Repository Reorganization

[razorace]

Hi guys, I'm seriously considering switching to Subversion for our code repository. If we do go ahead and make the switch, we can completely reorganize the files in a more logical order. Most specifically, Subversion allows us to store the Enhanced files in a different repository directory. Any additional suggestions on how to organize things beyond that?

 

Here's my basic idea:

/Basic/ - main Basic folder

/Basic/docs/ - documentation

/Basic/source/ - source code

/Basic/assets/ - non-dll assets for mod

 

/Enhanced/ - main Enhanced folder

/Enhanced/docs/ - documentation

/Enhanced/source/ - source code

/Enhanced/assets/ - non-dll assets for mod

[ensiform]

Will you be able to port the revision logs and such with the thing i suggested?

[razorace]

I'm not sure. How would I do that again?

[ensiform]

You need python for sure to run the script I think and you need access to your server :/ Maybe ask freerepo to do it?

[razorace]

well, I probably going import the whole repository to my university's Unix system and then move it into SVN. Where's the script to do this?

[Sushi_CW]

I'm all for it. But you probably already knew that...

 

That organization scheme looks good to me.

[ensiform]

well, I probably going import the whole repository to my university's Unix system and then move it into SVN. Where's the script to do this?

 

http://cvs2svn.tigris.org/

[razorace]

Doh, you need console root access to the machines for that to work. Oh well, I don't really need that revision data anyway.

[Vruki Salet]

Could you make a copy of it somehow (text file, screenshot, anything) and make that available before it's lost forever?

[razorace]

You mean of all the revision data? Well, the old CVS repository isn't going away, it's just not going to be used anymore. If people wanted the old data, they can still access the old repository.

[razorace]

The shiny new repository is up. Details here.