Re: [Valgrind-developers] 3.0 release and release numbering

[Tom H. <to...@co...>]

In message <Pin...@ch...>
          Nicholas Nethercote <nj...@cs...> wrote:

> On Tue, 19 Jul 2005, Tom Hughes wrote:
> 
> >>>> I have a patch to default to using a vex in the top level valgrind
> >>>> directory. It also fixes valgrind's makefiles to build vex if necessary.
> >>>> Combining that with a subversion external so that vex is checked out
> >>>> with valgrind should provide a solution.
> 
> How does the Subversion external work?

You create an svn:externals property on the parent directory listing
other things which should be checked out when that directory is checked
out.

So in this case we would create an svn:externals property on the top
level directory of valgrind that contained:

vex svn://svn.valgrond.org/vex/trunk

That would cause vex to be checked out into the vex subdirectory whenever
valgrind was checked out, and likewise for updates and so on.

Tom

-- 
Tom Hughes (to...@co...)
http://www.compton.nu/