1) Why do you want to put binaries and other produced files under a "source"
code control system?
2) If so, why do you want/need to put them in a different repository?
I don't believe Subversion can accomplish what you want to do; but, I'm not
an expert.
I'm just wondering why you'd want to do it.
Chuck
> -----Original Message-----
> From: Dirk Hoffmann [mailto:dh.discuss@web.de]
> Sent: Thursday, September 25, 2003 12:18 PM
> To: Subversion users mailing list
> Subject: Same Working Dir Different Repos?
>
>
> Hi,
>
> I'm quite new to subversion and am planning to use two
> different repos
> (possibly even served by different servers) which should be
> accessible
> from within the same working directory.
>
> The reason is that I want to build up two seperate systems:
>
> One managing the program sources as common.
>
> Another managing packages containing all the product files
> (binaries,
> docs, etc produced from the sources).
>
> The problem is, that sources and product files may be located in the
> same working dir.
>
> The first solution coming to my mind is to have different
> .svn-directories, of course named differently. Then you
> somehow have to
> tell the client to use these. Is there a way to do so or am I
> completely
> on the wrong path?
>
> I'm thinking about compiling different clients which use different
> .snv-dirs or one client which accepts a command line arg to tell it
> which .snv-dir to use.
>
> Any advice very much appreciated.
> Dirk
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Sep 25 16:31:44 2003