Mercurial question

General
1

I’m a first time user of a version control system.
as a single developer I decided to try version control using mercurial on the same mac ( OS X)
Now after tonnes of reading on the net I still do not know exactly where I should create repositories.
I have several projects and want to put them under version control.

My question is: should I create a repository in ever projects folder where my source resides, or can I have a repository area for all my projects.
What is the right way to do this ?

2

I recommend separate repositories for each project. This will make it much easier to track changes.

3

Hi Johann,

For me personally I create a repository for each project. I think that is the way most people here use both git & mercurial.

Craig

4

There is also an article from the XDev magazine on using mercurial and Xojo together. You can find it here

5

thanks to all,
so I should create a repository on every project folder, ok ?

6

Right. I don’t know which OS you are using, but if your path looks like this:
/users/johann/xojo_projects/project_a
/users/johann/xojo_projects/project_b
/users/johann/xojo_projects/project_c
You go into each directory and type “hg init” from a command line/DOS prompt.
Then “hg add” to add the files
Then “hg commit” to commit the files.
Then “hg log” will show you your first commit.

Before you do that though make sure you have setup your mercurial user file. On Windows it is mercurial.ini. On Linux & OS X I think it is .mercurial.

7

thanks Craig, that helps a lot

8

You are welcome Johann.

Now that you are starting to use VC the next trick is to be sure and perform commits and adds often so that you capture your history as you go along. I would not do the commits & adds as often as I would save a file/project, but rather I would do it at the end of the day or whenever I was about to make a large code change.

9

A very old rule of thumb (dating back to prehistoric RCS days) is that anytime that you make a change that will result in you compiling the new code to test the change, you should commit / check in that code before you compile.

Now, if we could just get VC support natively added to the IDE :P. There was an old request from pre-Fogbugz days, but that seems to have faded into the fog(z) of history.

10

+1

Is there a feedback case for this that you know of?

11

Used a Ouija board to call up the spirits of feature requests past and was rewarded with a new Feedback entry:

<https://xojo.com/issue/37736>

12

Well that is an interesting use for one of those. I usually use those to clean my windshields…(ba-dum, ching)

I added it to my top cases. It is in the 5th position.

13

You know we love you, right Norman? :s It’s job security.

14

Interesting, 19036 does not come up in the search results when I search for “Version Control”.