A couple of questions on getting Julia on the Mac

[Federico Calboli]

Hi All,

recently I had a few issues with updating Julia on my Ubuntu box, so yesterday I planed /usr/local/julia, and remade all from git repo.  What I found quite interesting is that the new Julia I got on Linux says:  

Version 0.2.0-463.r7849

Commit 78499d66a1 2013-03-13 13:59:21

while on my Mac (OS 10.8.2), which I successfully updated yesterday I get:

Version 0.2.0-461.raa26.dirty

Commit aa26358a37 2013-03-13 01:17:44*

That made me think whether I should scratch Julia on my Mac, and remake all from the latest git repo.  While pondering this I noticed that there is a Julia app for the Mac.  So the question is, what is the best way of having Julia on the Mac, and staying on the right development branch?

[Stefan Karpinski]

If you want to have a fixed 0.1 branch version, using Julia.app may be better, although building from source and staying on the release-0.1 branch would work well too and is more frequently updated. If you want to stay as up-to-date as possible with the 0.2 development branch then building from source and staying on master is the way to go. Of course, things might break on the development branch, both because of API changes and accidental breakage, both of which we try to minimize, but which do happen on master.

[Federico Calboli]

What branch does

git clone git://github.com/JuliaLang/julia.git

(and then regular git fetch; git merge origin)

give me? My guess is 0.2 but then how does one git the 0.1 branch? Most importantly why is my latest 0.2 Julia 'dirty' on one machine and not so on another?

BW

F

[Patrick O'Leary]

The default branch is master (currently the 0.2 development branch).

The 0.1 branch is release-0.1; actual releases are tagged commits on that branch.

[Jameson Nash]

to answer your other question: a "dirty" git branch has changed (or extra) files. `git status` will tell you which ones