Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

The main guide giude assumes that the your illumos-gate workspace resides in a directory named /code (likely located in your rpool) and owned by your build user.


  1. When working on many bugs, people can have several "code" workspaces maintained as ZFS-clones of one golden code repo, as summarized in Working on several bugs at once
    However they can want to share the package repository between such projects, and maintain one package depot once configured.
  2. Snapshooting the package repo before and after a build to check for differences, or to do a zfs send to another machine.
    rsync may be better though (since the rebuild would likely wipe the repo and create it anew, even if made up of mostly the same contents – zfs diff would be huge, but rsync data diff would only include changes).
  3. nfs/cifs-sharing of the package repo may be easier to set up if it is a separate dataset.
  4. It can be located separately from workspace – another pool, different hardware (i.e. ramdisk/SSD for compile workspace, HDD for package repo).

main guide