subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Sperling <s...@elego.de>
Subject Re: Best way to maintain patches to a 3rd party library?
Date Thu, 06 Jan 2011 23:41:43 GMT
On Thu, Jan 06, 2011 at 11:43:31AM -0500, NN Ott wrote:
> >
> > > >
> > > > I have a source library that I need to periodically import (and then
> > patch)
> > > > for use by my code base.
> > > >
> > > > The SVN Book seems to reccomend a "vendor branch" scheme where you keep
> > a
> > > > patched branch of the "vendor drops". This would work, except that I
> > loose
> > > > any history of the library development.  (The vendor also uses SVN and
> > gives
> > > > read-only access to their repo.)
> > >
> >
> >
> > The above steps can also semi-automated using svn_load_dirs:
> >
> > https://svn.apache.org/repos/asf/subversion/trunk/contrib/client-side/svn_load_dirs
> >
> >
> >
> Stefan,
> 
> That is what the SVN books recommended, but then I can not access the
> original commit history of the 3rd-party library.

If you can access their svn repository, you can also access their
commit history, no?

> (The other option is to use svn:external and patch manually.)
> 
> This is exactly the crux of my question:
> 
> Can I make a local (patched) branch of an svn:external?  That way I could
> pull updates as needed, but still retain access to the full commit history.

You'd need to manually (or some automated fashion) apply each commit
made to their repository to your own repository.
This is very tedious if they make a lot of commits.
And revision numbers between repositories wouldn't match up.

I don't understand what the real problem you want to solve is.
Maybe you want to browse their history without internet access?
If you want to browse their history without internet access, I would
recommend keeping an svnsync copy of their repository on your hard drive.

Stefan

Mime
View raw message