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

Best Practice for Libraries

From: Karl Heinz Marbaise <khmarbaise_at_gmx.de>
Date: 2004-06-04 23:22:11 CEST

Hi there,

i have a little problem:

I have a library which comprises of much files, but there
are two parts in which i have created using svn:externals.

The library i will call Main-Lib, Part 1 (PEAR-Part) and
Part 2 (jpgraph).

so i got the folling layout:

  +-- 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
So i will be able to handle the library as component library which can
combined as needed based on the project....

Kind regards
Karl Heinz Marbaise

Software Entwicklungs- und Beratungs Service  http://www.soebes.de
Dipl.Ing.(FH) Karl Heinz Marbaise            email: info@soebes.de
Tel.: 0241 / 16 91 210                        ICQ#: 135949029
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:16:57 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.