Re: Something looks like CVS modules

On Friday 11 November 2005 16:58, Petr Baudis wrote:

quoted

1. The problem with checkout - single checkout should checkout all needed
modules to build project. Update should also update all modules. The same
with commit.
2. Tags should be done on all modules. All modules should be able to be
in the same branch.

quoted

And in the same time one module should be able to exists in two or more
projects !

Then just have only a bunch of directories in your project root, and
that shall be your modules. :-)

(CVS modules don't work like that either, do they?)

As far as CVS tracks tags/branches separatly for each file, tags abd branches 
work well for modules.

Bunch of directories is almost what I want except tags/branches/history. CVS 
does not care if two directories have separate root/repos. All it wants -is a 
properly CVS dir.

But this is troublesome, and doesn't fit into GIT's model at all. Do you
have any concrete example of a scenario where something like this would
be useful?

For eaxmle: I have java lib A. I setup project B in this way:
B/src/
B/A/src

Have another project C:
C/src/
C/A/src

Both of them share the same code from library's module. I can tag them, edit, 
commit: do all work I usualy do. If I change something in B/A/src this will 
be updated into C/A/src.

This is what I dreaming about :-)