How can I maintain a modified version (a “vendor branch”) of third-party software using Subversion?
People frequently want to use Subversion to track their local changes to third-party code, even across upgrades from the third-party — that is, they want to maintain their own divergent branch, while still incorporating new releases from the upstream source. This is commonly called a vendor branch (the term long predates Subversion), and the techniques for maintaining one in Subversion are described here. If the vendor code is hosted in a remote Subversion repository, then you can use Piston to manage your copy of the vendor’s code. As a last resort, if using svn_load_dirs.pl is taking too much time or you’re looking for the lazy solution, see also Jon Stevens’ step-by-step explanation at Subversion Vendor Branches Howto. This solution does not make use of the space saving features in the Subversion backend when you copy new code over old code; in this solution, each import of a vendor code gets an entire new copy and there is no space savings for identical files.
People frequently want to use Subversion to track their local changes to third-party code, even across upgrades from the third-party — that is, they want to maintain their own divergent branch, while still incorporating new releases from the upstream source. This is commonly called a vendor branch (the term long predates Subversion), and the techniques for maintaining one in Subversion are described here.
Related Questions
- Can I use third-party commercial software, third party commercial boards or Microchip development systems with my contest entry?
- How can I maintain a modified version (a "vendor branch") of third-party software using Subversion?
- Which version of LabVIEW integrates with third-party source control software?
