How does Mercurial handle components or modular development?

Question

Currently using CVS ...

When creating a new project that references modular components, we use aliases to create a project directory. So, if it project1uses component1and component2, we will use aliases to pull these components into the directory project1so that

cvs co project1

Provided the developer with everything they needed - with components in subdirectories.

I understand that the equivalent in Subversion is equal svn:external, but may be incorrect.

My question is: how does this work with Mercurial? I heard people talking about expanding the forest and other modules, but I would expect such functionality to be clear enough (so I assume I missed something).

There is a related question , but I don't think this is a duplicate.

Thank you for your help.

Answer 1

Mercurial did not have an official way to do this until release 1.3. Now it supports sub repo . It was still considered experimental, but it was made from whole fabric by the creator of Mercurial, and it was a sticker for backward compatibility, so you are unlikely to stay tall and dry.

Answer 2

Mercurial has a DepsExtension that can be used for similar purposes, such as svn: external.