Thanks Christopher for your reply. I seemed to receive this directly
and not through the mailing list, so when I replied lastnight I didn't
address your post.
I will check out how sym links on Solaris will go and will update the
list when I find out.
Cheers,
Brooke
-----Original Message-----
From: Christopher [mailto:newsfilter@mann.fr]
Sent: Sunday, 12 September 2004 9:34 PM
To: I-Smith, Brooke
Subject: Re: Applications and Projects
Would the "link" function in version 1.1 take care of theres
considerations ?
An easy way of taking care of this would be in one repository
repos/App1
repos/App2
repos/Proj1
repos/Proj2
repos/Proj1/App1 <-------- IS A LINK TO App1
Now the internal revision numbers would go crazy : the file revision
numbers would change when proj 1 changes and vise-versa, but that
shouldn't be to big a deal.
Does the link functionality work as well with externals ?
Is Brooke Benjamin's concern mainly with avoiding a copy in the proj
directories ?
I don't see how it is possible to include a dependence on the external
project and not include versioning information on the external project.
Is that what Brook Benjamin wants to do ?
Brooke Benjamin Oehm Smith wrote:
> Gidday SVN-Users,
>
> This is the second post to a topic I posted a month ago but didn't
> receive a reply on. My post was possibly long and difficult to read.
> I'll try and simplify the question. (Note that I can't find my post in
> the archives - and now that I look it doesn't seem to have gone
> through - no wonder I didn't get any replies!).
>
> This is what I want - i have a number of applications where some main
> applications (lets call them projects) depend on some other
> applications and would like to have them exported at the same time (I
> will checkout and work on them independantly of any project). Before
> you yell out "svn:externals" let me say that I don't want these apps
> to be included inside the project like what svn:externals seems to
> do. I want the Apps independant of any projects and when updated (and
> reexported) then the modifications should be available to all
> projects. The Applications might be used independantly of any project
> aswell.
>
> The repository will look like the following. When the repository is
> checked out or exported then the structure will be similar:
>
> repos/App1
> repos/App2
> repos/Proj1
> repos/Proj2
>
> My understanding of svn:externals is that if I used externals then the
> repository export or checkout would have a structure that looked like
> (if the Apps were defined as externals in the projects):
>
> .../App1
> .../App2
> .../Proj1
> .../Proj1/App1
> .../Proj1/App2
> .../Proj2
> .../Proj2/App1
> .../Proj2/App2
>
> THAT IS NOT WHAT I WANT!
>
> Is there any easy way to achieve what I want using the existing
> vanilla SVN? I was thinking I may need to create my own property -
> say 'DEPENDS' and set this on the projects.
>
> svn ps DEPENDS "svn://server/repos/App1 svn://server/repos/App2" proj1
>
> and then write my own script to do exports. Maybe the property
> shouldl be 'exports'. Does this sound valid and the best way? Is
> this something others would want to do also?
>
> Any feedback or advice would be appreciated.
>
> BTW, I was able to use CVS modules to achieve this.
>
> Thankyou,
>
> Brooke
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Sep 14 09:41:25 2004