[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Modules which depend on each other -- how to handle?

From: Matthias Kaeppler
Subject: Re: Modules which depend on each other -- how to handle?
Date: Thu, 14 Apr 2005 13:54:11 +0200
User-agent: Debian Thunderbird 1.0 (X11/20050116)

Matthias Kaeppler wrote:

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?

Hm, no answers so far, okay, let me tell you how I intend to handle it and you tell me if that's good or bad.

My idea is to keep the widget as an own module in the repository, and add files to the program module which contain a widget definition derived from the one cvs controls for me. So I have solved the first problem, in that I have the extensions to the widget which are specific to the program in separate files and always in the right module.

I could then checkout the program module, enter the sandbox and in there checkout the module for the original, unmodified widget. In my program I would only work with the files which contain the definition of the derived widget, so the program sandbox could look like this:


whereas widget/ is the sandbox for the original, unmodified widget from which custom_widget inherits.

Okay, this is getting very specific now, but I guess this is a common problem which can be further generalized.

If I have more than one separate module on which my program depends, I could write a checkout/release script which handles the imports for me.

However, I hoped CVS has a built-in mechanism for handling project dependencies from the same repository.

Any comments?

Matthias Kaeppler

reply via email to

[Prev in Thread] Current Thread [Next in Thread]