You may use the Git or Mercurial source code management systems to retrieve the illumos source code. Both tools will be able to retrieve the same history. Ensure about 6 gigabytes of free space for the source and binaries combined.
Mercurial pulls a complete replica (clone) of the repository, including all history, from a remote source, and then updates a working copy of the files from this clone. The working copy is the files you may edit and compile. You may update the working copy from any versions of files in the repository history.
When cloning an external source code repository, Mercurial starts by creating a new directory, and fails if one already exists and is not empty. The directory may be a mountpoint for an empty ZFS dataset. Mercurial creates a
The following example creates a clone of the "Mercurial repository" ssh://email@example.com/illumos-gate containing the illumos source code under
/code; this will create a sub-directory
illumos-gate under that.
Updating the source with Mercurial
Mercurial pulls a complete replica (clone) of the repository from a remote source, and then updates your working copy of the files from this clone. The working copy is the files you may edit and compile. You may update the working copy from any versions of files in the repository history.
If you want to get latest version of
illumos-gate merged with your private development code, you need to
hg pull new changes into your repository clone and
hg update the working copy. This can be done in one command as
hg pull -u. If you have committed changes prior to updating, you may be wish to
hg merge them with the new changes.
For more details see: http://mercurial.selenic.com/wiki/FAQ.