[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Best-use scenario for vendor supplied libraries

From: Snay, Marc <Marc.Snay_at_turner.com>
Date: 2006-11-29 16:26:35 CET

I am tasked in my department to create a 'standards of use' document for
our SubVersion repository. In sending out my rough draft of the
document, one of the developer's posed the question of 'What about using
vendor supplied libraries'.


The on-line subversion book describes a system of using a /vendor branch
that keeps a /current and a tagged /x.x version folder and then copying
the folder into the /trunk code. It also describes how version updates
to the supplied libraries could be made by checking out the /current,
expanding the tar ball for the new version into this WC, and committing
the changes, tagging this, and viola...


I also have a developer who would rather just incorporate all necessary
vendor supplied libraries into his projects, and check them in/out with
his code. We have multiple projects in the repository, so this could
lead to several project folders having the same libraries stored, or
even several folders with different versions of the same library.


What would you consider to be the 'best-practices' when dealing with
these libraries, and do those practices change with libraries that are
actually compiled binaries as opposed to text-based Open-Source code?
Received on Wed Nov 29 16:27:28 2006

This is an archived mail posted to the Subversion Users mailing list.