svn move

bitplane · Post by **bitplane** » Sun May 20, 2007 5:21 pm

The svn repository is undergoing a long awaited directory structure change.

All source will now be in /trunk, external libraries will be held in /vendor, while releases and experimental code will be moved to /branches.

This will take a few commits since svn doesn't like me moving something twice without committing, I'll post again when it's complete.

bitplane · Post by **bitplane** » Sun May 20, 2007 8:36 pm

okay done..
please complain here or in bug reports if i broke anything!

edit:

The new URL for the latest code is https://irrlicht.svn.sourceforge.net/sv ... icht/trunk

hybrid · Post by **hybrid** » Sun May 20, 2007 11:38 pm

Wow, that was fast

I'm still downloading, so I don't know if something's failed. But the first impression was good. Thanks!

sRc · Post by **sRc** » Mon May 21, 2007 12:17 am

hmm, with the libraries moved to another folder, how does that affect building svn?

hybrid · Post by **hybrid** » Mon May 21, 2007 12:26 am

the libraries are in their original place as well . The vendor branch is used to store the original versions, while the copied versions are to store local modifications as well. Then you can merge in new versions more easily.

bitplane · Post by **bitplane** » Mon May 21, 2007 4:30 am

took me a while to figure out why I couldn't do a "svn copy" in the repository, I kept getting http 403 errors.
Turns out that it's a sourceforge bug - you need to add the project unix name as a subdomain of the svn host, so to use "svn copy" I needed to check the code out from https://irrlicht.svn.sourceforge.net/svnroot/irrlicht instead of https://svn.sourceforge.net/svnroot/irrlicht ..

I'll throw in some search engine spam for good measure: 403 Forbidden sourceforge commit svn move svn mv trunk error, solution!

On another note, I might have done things the wrong way around. I think I should have copied the snapshots then committed, then copied the main directories to trunk, followed by another commit, then finally removed the original copies. Apologies to everyone who's now had to download the bulk of the source 4 times over, this might have been avoidable

Oh well, you live and learn eh?

hybrid · Post by **hybrid** » Mon May 21, 2007 7:23 am

I'm not sure if this can be really avoided. As I understood SVN handles files on the client side as largely unrelated. So it won't notice the identity of the copies and would have downloaded everything nevertheless.

anylo · Post by **anylo** » Thu May 31, 2007 12:38 pm

bitplane wrote:All source will now be in /trunk, external libraries will be held in /vendor, while releases and experimental code will be moved to /branches.

I might be wrong (well, no I'm not), but usually releases are in /tags.

Anyway, current solution is much better than the old one.

EDIT:
Checkout last example in svn copy.

Virion · Post by **Virion** » Thu May 31, 2007 1:00 pm

I've tried and it works

svn co https://irrlicht.svn.sourceforge.net/svnroot/irrlicht irrlicht

Anyway, I'd also edited the link in wiki. Sorry for the late action.
Err well... anyone know where can I find the tutorial for building the source on window?

(I've just started to use svn today)

lester · Post by **lester** » Thu May 31, 2007 1:07 pm

just a notice
What to do with the the SkinnedMesh branch? does it have any purpose?

Luke · Post by **Luke** » Thu May 31, 2007 1:21 pm

the SkinnedMesh branch is the new animation system thing.

bitplane · Post by **bitplane** » Thu May 31, 2007 1:29 pm

i think the whole business of keeping releases in /tags is a cvs thing, people still do it for svn but I think it's mostly for tradition. There's no difference between a branch and a tag in svn.
anyway, we opted to go for just 3 dirs at the root, possibly adding one for tools at some later date

mispunt · Post by **mispunt** » Thu May 31, 2007 1:41 pm

bitplane wrote:i think the whole business of keeping releases in /tags is a cvs thing, people still do it for svn but I think it's mostly for tradition. There's no difference between a branch and a tag in svn.

When reading the official SVN documentation you will find that they suggest to create a /tags for releases. That way it is easier for people to find a specific release.

anylo · Post by **anylo** » Thu May 31, 2007 1:50 pm

Virion wrote:I've tried and it works
svn co https://irrlicht.svn.sourceforge.net/svnroot/irrlicht irrlicht
Anyway, I'd also edited the link in wiki. Sorry for the late action.
Err well... anyone know where can I find the tutorial for building the source on window? (I've just started to use svn today)

Re-edited wiki, correct command is
svn co https://irrlicht.svn.sourceforge.net/sv ... t[b]/trunk[/b] irrlicht

Always check out trunk if there's no specific reason to do otherwise.

anylo · Post by **anylo** » Thu May 31, 2007 1:56 pm

mispunt wrote:
bitplane wrote:i think the whole business of keeping releases in /tags is a cvs thing, people still do it for svn but I think it's mostly for tradition. There's no difference between a branch and a tag in svn.
When reading the official SVN documentation you will find that they suggest to create a /tags for releases. That way it is easier for people to find a specific release.

/Tags has nothing to do with CVS. It's been always "separate dev versions are in branches, releases are in tags".

Always do things as they are agreed to do, otherwise things like this might happen.

Irrlicht Engine

svn move

svn move

Re: svn move