[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Modules which depend on each other -- how to handle?
From: |
Matthias Kaeppler |
Subject: |
Modules which depend on each other -- how to handle? |
Date: |
Wed, 13 Apr 2005 17:32:41 +0200 |
User-agent: |
Debian Thunderbird 1.0 (X11/20050116) |
Hi,
I'm completely new to CVS so please forgive me any ignorant questions :)
My problem is:
I want to version-control two of my projects. One is a gtkmm widget, and
the other a gtkmm application, which uses this widget (I need to have
them in separate places though, because I might need to make changes to
the widget source code for the application which are extensions specific
to that app).
That means, I need the source code of the widget (the first CVS module)
always at hand in the sandboxes for the application. I have no idea how
I can make cvs doing this automatically for me, i.e. everytime I
checkout the newest version of the app, cvs should also fetch the newest
version of the widget source and put it in place.
Can you help me here?
--
Matthias Kaeppler
- Modules which depend on each other -- how to handle?,
Matthias Kaeppler <=