This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Moving C to its own directory (was Re: ObjC tree inlining)
- From: Karl Fogel <kfogel at newton dot ch dot collab dot net>
- To: Zack Weinberg <zack at codesourcery dot com>
- Cc: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>, Branko ?ibej <brane at xbc dot nu>, Phil Edwards <pedwards at disaster dot jaj dot com>, Neil Booth <neil at daikokuya dot demon dot co dot uk>, gcc at gcc dot gnu dot org, dev at subversion dot tigris dot org
- Date: 21 Nov 2001 17:58:54 -0600
- Subject: Re: Moving C to its own directory (was Re: ObjC tree inlining)
- References: <3BFBE544.9090500@xbc.nu><Pine.LNX.4.33.0111212304290.11430-100000@kern.srcf.societies.cam.ac.uk><20011121153330.X3915@codesourcery.com>
- Reply-to: kfogel at collab dot net
Zack Weinberg <zack@codesourcery.com> writes:
> There's a related problem, which we have now with CVS in the src
> repository, but would get worse if they were merged. CVS does not
> remember which module(s) you originally selected when you checked out
> a tree. Therefore, if you use the -d option, it checks out the entire
> repository the first time you try to update a working copy containing
> a subset of the tree. But if you don't use the -d option you don't
> get _any_ new subdirectories unless you specifically ask for them, and
> you may not know which they are.
>
> It would be nice if Subversion did this better.
I'm not sure it does (yet), except in that it versions directories,
but I don't think that exactly solves what you're talking about.
There have been various proposals for a Subversion module system,
along the lines of "union directories", or other indirection-based
systems that allow rule-based groupings. That would probably solve
the problem described above, but it will not be in 1.0.
On the other hand, Subversion will support symlinks / shortcuts, which
should alleviate the problem...
-K