Subversion QOTD
-
Hello all, I was wondering how do you solve this situation: When you have some files that are common to various projects, let's think on libraries or other kinds of files that must be shared, do you copy them in each project and when you want to update the library for all the projects you go project by project changing the local copy or do you have other methods implemented? I've thought on doing that change automatically, but I don't have any idea if this is possible or not, and moreover I'd like to be able to make some branches and to make the different projects to depend on the right branch... Any idea? As always thank you in advance...
-
Hello all, I was wondering how do you solve this situation: When you have some files that are common to various projects, let's think on libraries or other kinds of files that must be shared, do you copy them in each project and when you want to update the library for all the projects you go project by project changing the local copy or do you have other methods implemented? I've thought on doing that change automatically, but I don't have any idea if this is possible or not, and moreover I'd like to be able to make some branches and to make the different projects to depend on the right branch... Any idea? As always thank you in advance...
Joan Murt wrote:
I've thought on doing that change automatically, but I don't have any idea if this is possible or not, and moreover I'd like to be able to make some branches and to make the different projects to depend on the right branch...
You can write a shell script to execute your svn commands to check out the correct branches. You can then push this script to your dev team and users via subversion or another revision control system like bazaar. I use something like this to automate my build, test, and deploy enviroments
-
Hello all, I was wondering how do you solve this situation: When you have some files that are common to various projects, let's think on libraries or other kinds of files that must be shared, do you copy them in each project and when you want to update the library for all the projects you go project by project changing the local copy or do you have other methods implemented? I've thought on doing that change automatically, but I don't have any idea if this is possible or not, and moreover I'd like to be able to make some branches and to make the different projects to depend on the right branch... Any idea? As always thank you in advance...
-
Hello all, I was wondering how do you solve this situation: When you have some files that are common to various projects, let's think on libraries or other kinds of files that must be shared, do you copy them in each project and when you want to update the library for all the projects you go project by project changing the local copy or do you have other methods implemented? I've thought on doing that change automatically, but I don't have any idea if this is possible or not, and moreover I'd like to be able to make some branches and to make the different projects to depend on the right branch... Any idea? As always thank you in advance...
You want to look at externals in Subversion does exactly what you want, linking to differing repositories/branches and revision etc. You can set this up very easily using Tortoise if you want. http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-howto-common-projects.html[^]
-
Hello all, I was wondering how do you solve this situation: When you have some files that are common to various projects, let's think on libraries or other kinds of files that must be shared, do you copy them in each project and when you want to update the library for all the projects you go project by project changing the local copy or do you have other methods implemented? I've thought on doing that change automatically, but I don't have any idea if this is possible or not, and moreover I'd like to be able to make some branches and to make the different projects to depend on the right branch... Any idea? As always thank you in advance...
Like leppie, I create a folder in the root called 3rd Party Libraries. All projects that depend on the library reference it from here.
Tech, life, family, faith: Give me a visit. I'm currently blogging about: Upon this disciple I'll build my new religion? The apostle Paul, modernly speaking: Epistles of Paul Judah Himango
-
You want to look at externals in Subversion does exactly what you want, linking to differing repositories/branches and revision etc. You can set this up very easily using Tortoise if you want. http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-howto-common-projects.html[^]
-
You want to look at externals in Subversion does exactly what you want, linking to differing repositories/branches and revision etc. You can set this up very easily using Tortoise if you want. http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-howto-common-projects.html[^]
That's a very smart way of doing it. I'm going to have to update my setup and deploy scripts to take advantage of it.
A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. - -Lazarus Long
-
You want to look at externals in Subversion does exactly what you want, linking to differing repositories/branches and revision etc. You can set this up very easily using Tortoise if you want. http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-howto-common-projects.html[^]
-
We use externals as well. Our Trunk always points to the Trunks for the third-party libraries - but when we branch - we branch the third-party libraries as well so that our deliveries will not pull in 'untested' libraries..
You can also specify the revision to use for the external code/libraries so it will always bring back the compatible code. Eg Trunk ->External Shared Libs(Rev 12345) etc
-
You want to look at externals in Subversion does exactly what you want, linking to differing repositories/branches and revision etc. You can set this up very easily using Tortoise if you want. http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-howto-common-projects.html[^]
Hi all, I'm trying to use svn:externals, without success. My problem is when I type the property like: Folder structure: trunk Robot Common On common folder, I'm adding the property svn:externals Common svn://servidor01/$ Common Tortoise Svn gives me a parsing error. Why? Thank you in advance.
-
Hi all, I'm trying to use svn:externals, without success. My problem is when I type the property like: Folder structure: trunk Robot Common On common folder, I'm adding the property svn:externals Common svn://servidor01/$ Common Tortoise Svn gives me a parsing error. Why? Thank you in advance.
What is the url you would normally use for accessing the common folder? This should be exactly the same url you use for the tortoise external. I am not sure why you have a $ symbol and then the common folder name?
-
What is the url you would normally use for accessing the common folder? This should be exactly the same url you use for the tortoise external. I am not sure why you have a $ symbol and then the common folder name?
The repository is at svn://servidor01/$ Common ($ means nothing, can it cause any problem?) I would like to have this common project at this working copy of another project: c:\$ Projectes\projecte 153\ Can someone please tell me how can I use svn:externals? Thank you in advance