I have source code files that get used in several different projects (the language does not permit the equivalent of compiled .lib files very easily). It is not common for a project to require a custom-made version of such a file, but it is common for such a file to get updated within a project and then later brought back to a central location for distribution to other projects.
I originally thought of using hard or symbolic links in the CVS repository to simplify this problem, but I'm finding there are many dangers to this--unnoticed accidental link breakage, a rogue update breaking things on a company-wide scale, and of course, the joys of a project-specific branch finding its way into a central file. Multiply this last issue a few times, and you have the potential for one truly crazy development tree for a library file! So I'm now inclined to believe that this problem is not better solved by anything other than having multiple copies of each shared file. In this plan, I would have to check occasionally for differences among the HEAD revisions of each copy of each file to find updates, then individually commit those updates to each project. Of course, in branched projects on which development continues along branches, this compounds to include those branches. Is there a better way? I doubt it, but it seems there's no harm in asking. -- Doug Lee [EMAIL PROTECTED] http://www.dlee.org Bartimaeus Group [EMAIL PROTECTED] http://www.bartsite.com "Sometimes I think my learning curve is a circle." -- David Andrews _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
