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

Re: Best Practice for Libraries

From: <kfogel_at_collab.net>
Date: 2004-06-04 22:16:20 CEST

Karl Heinz Marbaise <khmarbaise@gmx.de> writes:
> lib
> +-- PEAR
> +-- jpgraph
> +-- much other directories.
> I have started a new little Project which doesn't need the jpgraph
> part. But if i use svn:externals 'lib svn://svn/svn/lib/trunk'
> i got of course the jpgraph part as well....
> In CVS this has been solved using differnt Ampersamp Module entries or
> aliases for differnt arrangements.
> Can someone make a good suggestion how it can be solved in a good way
> in SVN assuming that the library will grow and the number of sub parts
> too.
> So i will be able to handle the library as component library which can
> be
> combined as needed based on the project....

Well, you could include just the subdirs via svn:externals. That is,
instead of a prop value like this:

   lib http://myserver.org/repos/lib/trunk/

you would have this

   lib/PEAR http://myserver.org/repos/lib/trunk/PEAR
   lib/whatever http://myserver.org/repos/lib/trunk/whatever

and simply not include the 'jgraph' subdir.

Still, it might be easier just to get 'jgraph' and ignore it, unless
it's very inconvenient.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 4 23:37:42 2004

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.