qertler.blogg.se - Tortoisehg clone local repository

#TORTOISEHG CLONE LOCAL REPOSITORY CODE#

For example, when you clone a repo, Mercurial will recursively clone all of its subrepositories as well, so the developer (or build server) doesn’t need to know about the dependencies - the source control system handles it all. Subrepositories let you treat a collection of repositories as a group.

#TORTOISEHG CLONE LOCAL REPOSITORY CODE#

You don’t want to have to think, you want to write code and get things done. They’re not intractable issues by any stretch, but you do have to think about them.

Does the build server know about all this?.

Where on my disk does the library need to live?.

What version of the library should you clone?.

Should you write a script to fetch the dependencies or some build tool?.

How is this extra step communicated? Is it in a wiki document somewhere?.

The copy/paste method makes propagating changes a real nightmare, and the external reference approach has its own drawbacks: But what is the most efficient way to store and track a piece of code that is shared across dozens of projects? Should you simply copy and paste the library’s source code into a lib folder within each project’s repository? Or should you store the library in its own repository and reference it externally?

You can browse through it, debug into it, and make changes to it. Having the source code of a library that your project depends on is very beneficial. We should leverage code that we’ve already written, and use open source libraries and frameworks where appropriate. As developers, we don’t want to keep reinventing the wheel over and over again. I'm Rob: a developer + designer turned marketing executive.Ĭode reuse is important.