Question

I have a project I’m currently working on, which I am contemplating making open source, but I definitely want to keep it closed-source for the time being. Inside this project, I have a sort of subproject that I want to make public, so anyone can access/fork it.

So here’s what I want:

A mercurial SCC with:

• Repo 1: All files from /dir/project/ – Private repo, requires username/password to pull/push/fork/browse etc.
• Repo 2: Some files from /dir/project/stuff – Public repo, but requires username/password to modify.

How can I do this? Is there a better way I can do this? I’m using my shared hosting Linux environment to do this, so is symbolic linking a better idea?

I’m open to all suggestions thanks, still a bit of a HG newbie.

Answer 1

You should use “subrepository” to define the two parts of your project:

• your parent repo would be the private one, with a reference (in a .hgsub file) to your public repo ()
• your public repo woud be stored in a public referential, with no knowledge of the private part.

(No symlink necessary here)
See also in the same kind of problem the SO question “Mercurial Subrepos – How do you create them and how do they work?“.

Subrepositories is a feature that allows you to treat a collection of repositories as a group. This will allow you to clone, commit to, push, and pull projects and their associated libraries as a group.