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

Re: Why are branches real directories?!?!?!

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2003-04-03 00:10:21 CEST

"Jean-Luc Wasmer" <jl.subversion@wasmer.ca> writes:

> trunk/projects/projectA/Makefile
> trunk/components/componentA/
> trunk/components/componentB/
> branches/jlwasmer/projects/projectA/Makefile
> branches/jlwasmer/components/componentA/
> branches/jlwasmer/components/componentB/
>
> I can compile
> everything from trunk with trunk/projects/projectA/Makefile
> everything from the jlwasmer branch with
> branches/jlwasmer/projects/projectA/Makefile
>
> If I want to compile
>
> trunk/components/componentA/
> branches/jlwasmer/components/componentB/
>
> or
>
> trunk/components/componentB/
> branches/jlwasmer/components/componentA/
>
> I need to change the makefile or create a new one.

You have two options:

1. Checkout a working copy of /trunk.

    'svn switch' your componentB subdirectory to reflect
    /branches/..../componentB.

    Do you really need a new Makefile for that? Is the branch of
    componentB so different that the Makefile in /trunk won't be able
    to compile it? Notice that no paths have changed in your working
    copy at all... just file contents.

2. Create an empty directory in the repository which uses the
    svn:externals property, and have it "pull together" components
    from different locations when you checkout a working copy.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Apr 3 00:12:59 2003

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