Re: commit when using svn:externals

[kf...@collab.net]

"Adam MacBeth" <Ad...@portalplayer.com> writes:
> I'm trying to find a replacement for CVS aliases and the svn:externals
> property seems to be the closest thing.  After reading the last
> paragraph in the Externals Definitions section in the subversion book,
> it seems like this doesn't quite match up, though.  Are there plans to
> add the ability to do a single "svn commit" instead of having to commit
> in each auxiliary copy?

Not in the near future.  Eventually, yes -- but I don't think we can
give you a date that would change your planning.

See 

   http://subversion.tigris.org/issues/show_bug.cgi?id=1167
   http://subversion.tigris.org/issues/show_bug.cgi?id=937

-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: commit when using svn:externals

[Nik Derewianka <su...@e-media.com.au>]

kfogel@collab.net wrote:

>"Adam MacBeth" <Ad...@portalplayer.com> writes:
>  
>
>>I'm trying to find a replacement for CVS aliases and the svn:externals
>>property seems to be the closest thing.  After reading the last
>>paragraph in the Externals Definitions section in the subversion book,
>>it seems like this doesn't quite match up, though.  Are there plans to
>>add the ability to do a single "svn commit" instead of having to commit
>>in each auxiliary copy?
>>    
>>
>
>Not in the near future.  Eventually, yes -- but I don't think we can
>give you a date that would change your planning.
>
>See 
>
>   http://subversion.tigris.org/issues/show_bug.cgi?id=1167
>   http://subversion.tigris.org/issues/show_bug.cgi?id=937
>
>-Karl
>

I am still trying to get upto speed on subversion at the moment so 
please forgive me if there is a way around this already.  We are using 
svn:externals as well to provide a common set of libs to all current 
projects - two things we are seeing:

1)  Our projects touch the lib files even if the author isnt making any 
changes (this is due to macromedia director which we cant modify ).  The 
author commits the files in the project but when goes to update gets 
blocked by the changed local lib files - is there someway to clear the 
fact that they have been touched, or to make the update ignore those 
local lib files ??

2) We have noticed that sometimes when doing a commit/update on projects 
that have the svn:externals property that we get an svn protocol error.  
Manually going into the libs folder (which was defined as an external) 
and doing a seperate update on it and then going back to the project 
folder and retrying the update usually works.  Just wondering if anyone 
has seen this or whether im doing something wrong.

BTW all of this is on win32 using svnserve 1.0.   Have yet to try 1.0.1, 
but await the win32 binaries to start testing.

I have to admit that svn:externals is the closest thing coming to the 
modular functionality we need for our projects - big thanks to whoever 
can get this feature working completely.

Regards,
Nik

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org