SVN should use externals or vendor branches to bring in outside code

[GoogleCodeExporter]

To make things more consistent and easy to build, either svn externals or a 
vendor branch should 
be setup for outside code.  This will reduce the number of steps to build the 
toolchain as well.

http://weierophinney.net/matthew/archives/132-svnexternals.html

http://svnbook.red-bean.com/en/1.2/svn.advanced.vendorbr.html

Original issue reported on code.google.com by dmun...@gmail.com on 12 Sep 2007 at 1:11

[GoogleCodeExporter]

marked as enhancement

Original comment by Phi...@gmail.com on 12 Sep 2007 at 1:13

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Ok, we use externals now. However, this doesn't really do what we want to do: 
vendor branches aren't helpful 
because they force us to commit the entire tree to SVN, which would exceed our 
quota, and externals are nice 
but they don't let us override specific files without outside support. So it 
looks like fill-llvm-gcc.sh is going to 
have to stick around, although it doesn't require an internet connection now.

Original comment by nightwat...@gmail.com on 12 Sep 2007 at 5:26

• Changed state: Fixed