svn-externals

this is the workflow I currently use for my svn projects (I never use svn branches, and some projects are actively worked on by other people as well): on the server, do the inital git svn fetch which might take hours. Also create a 'build' branch. on a development machine cloning is now fast: git clone srv://project.git, git checkout build followed by git update-refs ..., git svn fetch to restore the link to the svn repository work, commit, work commit, ... to check if things are sane, git push build to the server and trigger a build in Hudson for that branch to store work so that I can work

I would not get to know svn:externals if I haven't run into the this page . So, I setup my working folder. Then mkdir lib/vendor svn add --parents lib/vendor svn ps svn:externals 'symfony http://svn.symfony-project.com/branches/1.4/' lib/vendor/ svn ci -m "add externals" svn update The "svn update" enlists the whole symfony folder and is pretty slow. I thought that would be single time pain. However, SVN will check external repository every time I typed "svn up". I have to use --ignore-externals to make "svn update" fast enough. I'm wondering what's the benefits of svn:externals if it is so

I've a very large subversion repository, it's about 7 GB in size and holds many many files and directories from different projects. Now I did some major change to one project structure which is actually a library and I'm using it in quite a few other projects within the same repository. Now the documentations is sparse and I don't know which project actually really used this library as external and I'd like to somehow query the subversion server/repository to return me all directories which have a certain string in the svn:export property so I can adjust them. Ideally without checking out the

When you check out a git repository that contains svn externals, it will simply ignore them. What people have done is create many scripts, many of them mentioned in this question How do I keep an svn:external up to date using git-svn? . The problem is that while numerous scripts are floating on the internet, I have yet to find one that was actually robust. By robust, I mean specifically: It can handle svn externals pegged to a particular revision It can handle svn externals that point to a file instead of a directory Because these are 2 issues with my repository that seem to bring most scripts

I'd like to evaluate Mercurial for my working projects. But most of my projects very heavily rely on the presence of svn:externals-like support. I've searched over StackOverflow and googled for corresponding support in Mercurial. All I found is subrepo feature added in Mercurial 1.3, but the page for this feature said: subrepos are an experimental feature for Mercurial 1.3. So don't do this on mission critical repositories! I don't want to use something unstable. Can anybody shed some light on the real status of this feature, and the plans of polishing/finishing it and when it will be called

We are considering a move from SVN to Mercurial, and have encountered a stumbling block. We currently use svn:externals to automatically pull a common set of libraries into the working directory. I can't find support for anything like this in Mercurial. Is there a way to do this automatically with Mercurial, or do I need to fake it as part of my build process? Ry4an Brase There's no good way to do it using mercurial only. The Forest Extension mentioned elsewhere causes more problems that in fixes nowadays. Most folks just use a large repo and include all their components in the repo and then

I have a repository for one of my projects that has a nested repository using the svn:externals property to update files from an external library. The problem is that I need to comment out one of the function declarations from one of the headers in this library, and carry around the modified header with the root repository. Is there a way that this could be done, so that when the library is updated, it overrides that specific file with my version of it? What you want sounds like a "vendor branch" scenario to me. current repository root |-- myproject | -- mycode | -- library -> svn:externals to

Can we set a single file as external in Subversion? Yes, it's possible with svn 1.6. It's documented in the nightly build version of the svn book. But even though file externals are working, you should only do it with text files (for now) because binary files won't work correctly as file externals. As mentioned in the first answer, SVN Externals are documented in Chapter 3 of the SVN Book , and quite a few syntax examples are given there. In addition, this note is given: "Because the svn:externals property has a multiline value, we strongly recommend that you use svn propedit instead of svn