How to organize Repository RE-use code

[P@Anand]

---

@Stranman wrote:

What is the Subversion behavior when a module that is part of its own repository is added and included into a project that has a repository. 

Does the module maintain its link to its originating repository?

Thanks,

- P

---

When you copy the Module into the Project's repository then the "Module" will be included to the Project's repository (You have the option to added when you commit) and it will not have any link to its own repository. Why because it is just the copy of the files and you cannot move the repository link by moving the files in the drive. If you just access the module from the Project without physically moving the files then both will maintain individual repositories.

This is turning out to be a Sub Version thread totally :).

[crossrulz]

---

@Stranman wrote:

What is the Subversion behavior when a module that is part of its own repository is added and included into a project that has a repository. 

Does the module maintain its link to its originating repository?

Thanks,

- P

---

If the file is copied, then each repository will have its own copy of the VI.  If you just include it in your project, but the file is left where it was (ie, in the other project's work directory), then only the original repository will have a copy of it.  I recommend going with the latter.

[mikeporter]

The whole point of having a reuse library is that you have one standard codebase that you link against - so you don't copy it anywhere. If you standardize on a directory structure it will make things easier.

You also don't include the reuse code in your projects directly. When you use them and they will show up in dependencies, which is all that is needed.

Mike...

[Yamaeda]

There's also the advanced version of linking repositories, you can create a "virtual" folder structure that checks out from several repositories yet keep their original linkage.

This could e.g. be nice if you have a library of drivers and classes in a central place but dont want to link outside of your project folder, this way you can have the best of both worlds. It is a bit messy/advanced to set up though.

/Y

[mikeporter]

I never thought of it as particularly messy or advanced - just organized. You have separate repositories for your projects and for your common code. As long as the relative position of the code doesn't change when you create you working copies, nothing has to relink.

Mike...

[Yamaeda]

If you want your common code to be in the same structure as your project yet still be in a common directory you'll need Externals, as described here: http://svnbook.red-bean.com/en/1.0/ch07s03.html

It can also be used with a revision option, so you know you're using a stable code version.

Maybe it's not that advanced when you get used to it, i've only tested it once.

/Y