Vishal [mailto:vsapre80@yahoo.com]:
> Subject: RE: How to organize a Subversion based code tree
>
> That is exactly my problem also. I have some common files which are used intermittently by other
> software components in the projects.
>
> The projects as such are independent but due to common files (common utilities) its getting
> difficult to define what would the complete repository look like.
In my case, common files are 'common subprojects' which are handled as
'full projects'. As I have one repository per project this means common
files live in parallel to the 'full' files and can be referenced by
relative paths if people check out projects into parallel directories.
> Also, when I check out Project A, I just need the trunk not the tag
> or the branch folders. Is there an automated solution for it or does
> it need to be done manually.
There is the 'svn:externals' property which is presumably created to
solve such problems but I have found it more difficult to work with
than with completely separate projects.
Andre'
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 3 06:31:58 2005