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

Pattern matching with external definitions

From: Dave Hotchkiss <dave_at_supercomputerinc.com>
Date: 2005-03-16 19:38:03 CET

Is there any way to effectively use pattern matching with external
definitions? Since external definitions only work with URLs and only
at a directory level, I'm not sure of a way to do it that doesn't
involve manual intervention.

Example: Suppose I have two repositories as laid out below.
Repository A is my own code, and it has a /third-pary/includes
directory with external definitions that point to *.h files in another
repository. Repository B is a set of third-party files that includes
a large directory with several *.h files mixed in with other file
types. My goal is to have repository A set up such that a user can
do a fresh checkout and the code will build from there. Here is a
sample *desired* file layout:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Repository A (my code)
-------------
bigapplication
   /src
      bigappfile1.c
      bigappfile2.c
      bigappfile3.c
    /includes
      bigappfile1.h
      bigappfile2.h
      bigappfile3.h
    /third-party
       /includes
          magicfile1.h [external def]
          magicfile2.h [external def]
          magicfile3.h [external def]

Repository B (third-party files)
-------------
magiclibs
   /src
      magicfile1.c
      magicfile1.h
      magicfile2.c
      magicfile2.h
      magicfile3.c
      magicfile3.h
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

So, back to the root question: Is there a slick way to set up that
/third-party/includes directory in repository A? Obviously, we could
manually divide the files in repository B into separate directories,
but the third-party files unpack all together (as above) and I'm trying
to avoid manual steps. The way that we have it now is to have an
/include directory in repository B that actually has a copy of the *.h
files from the /src directory! Thus, in our current situation,
repository B actually looks like this:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
magiclibs
   /src
      <as above>
   /includes
      magicfile1.h [copied from ../src directory]
      magicfile2.h [copied from ../src directory]
      magicfile3.h [copied from ../src directory]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Any ideas to eliminate or streamline the manual intervention and/or
redundancy involved? Thanks very much.

-- 
Dave Hotchkiss
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Mar 16 19:41:30 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.