From c41b111c377c6036aab5ec63b6cee4d6c8571fdb Mon Sep 17 00:00:00 2001 From: Slava Kim Date: Wed, 4 Feb 2015 12:36:39 -0800 Subject: [PATCH] Add some documentation on the relation between unibuild, isopack and isobuild --- tools/isopack.js | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/tools/isopack.js b/tools/isopack.js index 4471d7eb13..f76736d46f 100644 --- a/tools/isopack.js +++ b/tools/isopack.js @@ -187,7 +187,19 @@ _.extend(Unibuild.prototype, { // Isopack /////////////////////////////////////////////////////////////////////////////// -// XXX document +// Meteor has a packaging system called "Isobuild". Isobuild knows how to +// compile the same JavaScript code-base to different architectures: browser, +// node.js-like server environment (could be Rhino or other) or a webview in a +// Cordova mobile app. +// +// Each package used by Isobuild forms an Isopack. Isopack is a package format +// containing source code for each architecture it can be ran on. +// Each separate part built for a separate architecture is called "Unibuild". +// +// There are multiple reasons why we can't call it just "build" and historically +// the name "Unibuild" has been associated with parts of Isopacks. We also can't +// call it "Isobuild" because this is the brand-name of the whole +// build/packaging system. var Isopack = function () { var self = this;