You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Ch...@qimonda.com on 2006/09/06 12:45:37 UTC
Subversion modules?
Does Subversion have a concept of "modules" as CVS did?
--------------------------------------
Chris T Fouts
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: Re: Subversion modules?
Posted by Mark Phippard <ma...@softlanding.com>.
<Ch...@qimonda.com> wrote on 09/06/2006 09:14:33 AM:
> But it's not "just for the sake of implementing it" - I (and others)
> used the feature! I'll look into svn externals as Mark Phippard
> suggested. Thanks folks!
It is not your fault, you just walked into one of several areas that has
been the subject of mini flare-ups in the past and your somewhat snarky
comment caused the reaction you got.
The truth is that svn:externals is Subversion's take on CVS modules. It
handles some scenarios quite well, and others not so much. So most people
would shy away from saying that is the "equivalent" of modules until they
know your use case.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: Re: Subversion modules?
Posted by Ch...@qimonda.com.
But it's not "just for the sake of implementing it" - I (and others)
used the feature! I'll look into svn externals as Mark Phippard
suggested. Thanks folks!
>-----Original Message-----
>From: Andy Levy [mailto:andy.levy@gmail.com]
>Sent: Wednesday, September 06, 2006 9:03 AM
>To: Fouts Christopher (QNA RTP PT PREV)
>Cc: users@subversion.tigris.org
>Subject: Re: Re: Subversion modules?
>
>On 9/6/06, Chris.Fouts@qimonda.com <Ch...@qimonda.com> wrote:
>> Ok, chalk this one to Subversion's intentionally missing
>features too!
>
>Or intentionally not implementing something "just for the sake
>of implementing it" because there are
>other/different/better/more flexible ways of doing things by
>not locking into another product's philosophy.
>
>> My use case: Part of our repository are our test cases. So when we
>> developers check it out, we check out everything. However, when we
>> distribute our code, we don't want to include the test case dir
>> structure. I know an alternative will be to store the test cases in
>> their own repository.
>
>Or keep the test cases in a different location in the same repository.
>Or have your process that creates the distribution package
>remove the test cases before packaging.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Re: Subversion modules?
Posted by Andy Levy <an...@gmail.com>.
On 9/6/06, Chris.Fouts@qimonda.com <Ch...@qimonda.com> wrote:
> Ok, chalk this one to Subversion's intentionally
> missing features too!
Or intentionally not implementing something "just for the sake of
implementing it" because there are other/different/better/more
flexible ways of doing things by not locking into another product's
philosophy.
> My use case: Part of our repository are our test
> cases. So when we developers check it out, we check
> out everything. However, when we distribute our
> code, we don't want to include the test case dir
> structure. I know an alternative will be to store
> the test cases in their own repository.
Or keep the test cases in a different location in the same repository.
Or have your process that creates the distribution package remove the
test cases before packaging.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: Re: Subversion modules?
Posted by Mark Phippard <ma...@softlanding.com>.
<Ch...@qimonda.com> wrote on 09/06/2006 08:59:35 AM:
> Ok, chalk this one to Subversion's intentionally
> missing features too!
>
> My use case: Part of our repository are our test
> cases. So when we developers check it out, we check
> out everything. However, when we distribute our
> code, we don't want to include the test case dir
> structure. I know an alternative will be to store
> the test cases in their own repository.
The svn:externals feature would work fine for this. In your script that
you use to distribute your code, you are likely going to run a command
like svn export. You would just use the --ignore-externals option on the
command. When developers checkout, the externals would be processed and
pull the test code into their working copy.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: Re: Subversion modules?
Posted by Ch...@qimonda.com.
Ok, chalk this one to Subversion's intentionally
missing features too!
My use case: Part of our repository are our test
cases. So when we developers check it out, we check
out everything. However, when we distribute our
code, we don't want to include the test case dir
structure. I know an alternative will be to store
the test cases in their own repository.
-chris
>-----Original Message-----
>From: M. Rohrmoser [mailto:mr.news.002@gmx.de]
>Sent: Wednesday, September 06, 2006 8:53 AM
>To: users@subversion.tigris.org
>Subject: Re: Subversion modules?
>
>Chris.Fouts@qimonda.com wrote:
>> Does Subversion have a concept of "modules" as CVS did?
>
>No. What's your use-case?
>
> M
>
>---------------------------------------------------------------------
>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
Re: Subversion modules?
Posted by "M. Rohrmoser" <mr...@gmx.de>.
Chris.Fouts@qimonda.com wrote:
> Does Subversion have a concept of "modules" as CVS did?
No. What's your use-case?
M
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Subversion modules?
Posted by Erik Huelsmann <eh...@gmail.com>.
On 9/6/06, Chris.Fouts@qimonda.com <Ch...@qimonda.com> wrote:
> Does Subversion have a concept of "modules" as CVS did?
No, but if you want to use the "ampersand module" setup in CVS, this
is what you can do:
- Create your source tree
- Create an empty directory in the location where you want to store your tests
- Store your tests elsewhere *in the same repository*
- Check out the project
- Switch the (empty) tests directory to the repository location the
tests are located at (svn switch /path/to/wc/tests/dir
REPOS-URL-TO-TESTS)
That way, commits to your source tree will also commit the changes to
the tests in the same commit. Updates will retrieve the latest changes
to the tests. Commits will be atomic across tests and source tree.
HTH,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org