On 11/23/2010 11:39 AM, Daniel Shahaf wrote:
Les Mikesell wrote on Tue, Nov 23, 2010 at 11:03:11 -0600:
The current version uses the directory structure of your workspace to
hold the repository information, so it sort-of makes sense that you
can't mix files from different repositories in the sam
Les Mikesell wrote on Tue, Nov 23, 2010 at 11:03:11 -0600:
> The current version uses the directory structure of your workspace to
> hold the repository information, so it sort-of makes sense that you
> can't mix files from different repositories in the same directory.
And why would this argum
Bastien Semene wrote on Tue, Nov 23, 2010 at 17:51:00 +0100:
> Ok, I just tested.
>
> There actually are 2 problems when I first tested the cross repositories
> file external, the first message I had was :
> Repository UUID '55a45616-c74e-de11-b3fa-001e4f22e0e6' doesn't match
> expected UUID '2
On 11/23/2010 10:51 AM, Bastien Semene wrote:
Ok, I just tested.
There actually are 2 problems when I first tested the cross repositories
file external, the first message I had was :
Repository UUID '55a45616-c74e-de11-b3fa-001e4f22e0e6' doesn't match
expected UUID '20aedb48-35eb-0310-b593-edfe3
Ok, I just tested.
There actually are 2 problems when I first tested the cross repositories
file external, the first message I had was :
Repository UUID '55a45616-c74e-de11-b3fa-001e4f22e0e6' doesn't match
expected UUID '20aedb48-35eb-0310-b593-edfe3b26aac3'
So I changed the UUID of my test r
Bastien Semene wrote on Tue, Nov 23, 2010 at 14:43:21 +0100:
> Is it still not possible to use file externals pointing on different
> repositories ?
It is not possible (because the code used to implement in 1.5 and 1.6
them assumes that the target URL belongs to the same repository).
I don't re
On 11/23/2010 8:09 AM, David Weintraub wrote:
I find the best way is to just make BAR a releasable subproject. You
could zip up its source code or compile bar into some sort of object
file that FOO can use (a jarfile for a Java project, or a *.dll or
*.so for C or C++ projects). Then, I'd have m
On 23-11-2010 15:46, Bastien Semene wrote:
From Piotr Kabacinski response (I compiled the mails) "You can use
relative path when accessing the same repository"
This is exactly the ambiguous use of terms I'm talking about. I can
think that I can't use svn:externals on different repositories, but
> From: Piotr Kabacinski [mailto:pi...@kabot.net]
> Externals to different repositories are possible.
> http://svnbook.red-bean.com/en/1.5/svn.advanced.externals.html
> You can use relative path when accessing the same repository.
>
> Problem is if you want to point to file (not to directory) -
Yes, I have different repositories hosted by the same Apache vhost (with
the SVNParentPath directive), and I can use relative paths to make
externals of folders between different repositories (different databases).
And they actually are on different hosts thanks to NFS.
From Piotr Kabacinski r
On 11/23/10 7:52 AM, Piotr Kabacinski wrote:
Hi,
Externals to different repositories are possible.
http://svnbook.red-bean.com/en/1.5/svn.advanced.externals.html
You can use relative path when accessing the same repository.
Problem is if you want to point to file (not to directory) - that, in fa
On Tue, Nov 23, 2010 at 8:43 AM, Bastien Semene
wrote:
> Hi,
>
> I read in the svn-book that file externals are supported only in the same
> repository. But it is not clear in my repositories architecture :
>
> My repositories are accessed through Apache and all use the same FQDN/vhost.
So, you
Hi,
Externals to different repositories are possible.
http://svnbook.red-bean.com/en/1.5/svn.advanced.externals.html
You can use relative path when accessing the same repository.
Problem is if you want to point to file (not to directory) - that, in
fact, is not possible.
greetings
On 23-11-2
13 matches
Mail list logo
