forked from meteor/meteor
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
also lower-case links so they render correctly in "Preview Changes"
- Loading branch information
1 parent
21e7154
commit 56d8173
Showing
1 changed file
with
17 additions
and
17 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -3,29 +3,29 @@ A list of terms and what they mean in Meteor context. This document is intended | |
|
|
||
| If you are reading Meteor code or Meteor docs anywhere and you find that a term is not clear enough or Meteor has used the term in a way that is not easy to understand please submit a PR adding a new term to this glossary. You don't need to be afraid of being wrong, we will review the PR and we can define the term in the best way possible in the review process. | ||
|
|
||
| ## Core package | ||
| A core package is of course a Meteor package. They are maintained in the official Meteor repo. | ||
|
|
||
| Core packages don't have .versions file as they are always released from a checkout of Meteor. | ||
|
|
||
| Every package that lives exactly in the folder `packages/` in the Meteor repository is considered a core package. If the packages lives in sub-folders of `packages`, like `deprecated` or `non-core` they are not considered a core package. | ||
|
|
||
| ## Isobuild | ||
| 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. | ||
|
|
||
| related terms: [Isopack](#Isopack), [Unibuild](#Unibuild) | ||
| related terms: [Isopack](#isopack), [Unibuild](#unibuild) | ||
|
|
||
| ## Isopack | ||
| 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". | ||
|
|
||
| related terms: [Isobuild](#Isobuild), [Unibuild](#Unibuild) | ||
|
|
||
| ## Unibuild | ||
| 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. | ||
|
|
||
| related terms: [Isobuild](#Isobuild), [Isopack](#Isopack) | ||
| related terms: [Isobuild](#isobuild), [Unibuild](#unibuild) | ||
|
|
||
| ## Core package | ||
| A core package is of course a Meteor package. They are maintained in the official Meteor repo. | ||
| ## Isopackets | ||
| Isopacket is a set of isopacks. Isopackets are used only inside meteor-tool. | ||
|
|
||
| Core packages don't have .versions file as they are always released from a checkout of Meteor. | ||
| An isopacket is a predefined set of isopackages which the meteor command-line tool can load into its process. This is how we use the DDP client and many other packages inside the tool. The isopackets are listed a constant called ISOPACKETS. | ||
|
|
||
| Every package that lives exactly in the folder `packages/` in the Meteor repository is considered a core package. If the packages lives in sub-folders of `packages`, like `deprecated` or `non-core` they are not considered a core package. | ||
| related terms: [Isopack](#isopack), [meteor-tool](#meteor-tool) | ||
|
|
||
| ## meteor-tool | ||
| This is the Meteor command-line tool. Most of the code for it is in the [tools directory](https://github.com/meteor/meteor/tree/devel/tools) of the Meteor repository. | ||
|
|
@@ -34,9 +34,9 @@ The Meteor tool also includes testing functionality and example apps for the Met | |
|
|
||
| It also defines the version of Meteor, when we say that you are using Meteor 1.12.1 that means you are using [email protected]. | ||
|
|
||
| ## Isopackets | ||
| Isopacket is a set of isopacks. Isopackets are used only inside meteor-tool. | ||
| ## Unibuild | ||
| 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". | ||
|
|
||
| An isopacket is a predefined set of isopackages which the meteor command-line tool can load into its process. This is how we use the DDP client and many other packages inside the tool. The isopackets are listed a constant called ISOPACKETS. | ||
| 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. | ||
|
|
||
| related terms: [Isopack](#Isopack), [meteor-tool](#meteor-tool) | ||
| related terms: [Isobuild](#isobuild), [Isopack](#isopack) | ||