You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Jan Keirse <ja...@tvh.be> on 2011/01/19 10:12:02 UTC

Betr.: Questions about svn:externals

David Aldrich <Da...@EU.NEC.COM> schreef op 19/01/2011 10:02:43:

> Hi
> 
> I wonder if anyone would answer the following questions about svn:
> external for me please?
> 
> 1) Subversion allows you to commit a change within the directory 
> that uses the svn:external property. This change will not be 
> committed to the referenced (source) directory/repo. I can't imagine
> a circumstance where one would want to do this, so how can we 
> prevent such commits being made?

Why? Imagine your project references an external project. While working on 
your project you notice a bug in that external project. You can fix the 
error and commit, without having to do a seperate checkout first, isn't 
that a good thing?

> 2) What would happen if the developer did not have read access to 
> the repo that is referenced in the svn:external? Would a checkout of
> the project that uses the external complete without error, except 
> that the external code would not appear?

My guess is that the project will be checked out without the external 
code, but that you will get an error message about that, I'm not sure 
though. 

Kind Regards,

JAN KEIRSE
ICT-DEPARTMENT
Software quality & Systems: Software Engineer

**** DISCLAIMER ****

http://www.tvh.com/newen2/emaildisclaimer/default.html 

"This message is delivered to all addressees subject to the conditions
set forth in the attached disclaimer, which is an integral part of this
message."