AW: Advice on repository design for multiple projects using shared source

[wrmarvin]

Thank you Felix for your response.

I am a novice with Mercurial, but my concern is that your proposed approach
would create one large single repository.  You would then have to clone the
entire thing.  What I want to do is to clone only a single VB project and
then when committing it back be able to keep track of change comments only
for that one VB project.

I can handle getting the VB projects to reference source code modules in a
different folder via relative paths.  I was thinking of putting the common
source code into its own repository and each VB project in its own
repository with its unique source.  To work on the project a developer would
clone the primary VB project repository and also have to clone the common
source repository into locations that have the same relative path
relationships.  Each cloned repository would then have to individually be
pushed back to the main repository and individually committed.  Instances
and comments of the individual VB project repository and the common source
repository would then be tracked and commented separately.

Ideally, I want a repository that holds a single VB project with its unique
code modules and forms.  This repository would have a "linked"
remote-repository that contains the shared source modules.  When cloning the
main VB project repository, a clone of the linked remote-repository would
also be automatically performed.  Pushes and commits would happen to both
repositories simultaneously and individually, but with a single action by
the developer.  The single action commit would prompt for individual
comments for each repository commit.

As I said, I am new to Mercurial and wanted to know if there is a common
practice or "best practice" for handling "shared source" (not shared library
routines (dlls) which are projects and repositories themselves).

I appreciate all advice about how to proceed with setting up a repository
system for my situation.
Bill

-- 
View this message in context: http://mercurial.808500.n3.nabble.com/Advice-on-repository-design-for-multiple-projects-using-shared-source-tp2366922p2384060.html
Sent from the General mailing list archive at Nabble.com.