official TinyOS release version on which the code is based, and `tmiver` is the
version of the modifications applied by TMI. Released APT package versions are
associated with tags in the source code repository. Consider the latest
-package version, 2.1.1-4.4, for which these tags exist in the repository:
+package version, 2.1.1-4.5, for which these tags exist in the repository:
-* `debian/2.1.1-4.4-1tmi` is the tag of the 'debianized' code from which the APT
- packages version 2.1.1-4.4-1tmi were built.
+* `debian/2.1.1-4.5-1tmi` is the tag of the 'debianized' code from which the APT
+ packages version 2.1.1-4.5-1tmi were built.
-* `release/2.1.1-4.4` is the tag of the TinyOS code of which
- `debian/2.1.1-4.4-1tmi` is a superset, the latter containing the debian
+* `release/2.1.1-4.5` is the tag of the TinyOS code of which
+ `debian/2.1.1-4.5-1tmi` is a superset, the latter containing the debian
packaging files.
-* `tinyos/2.1.1` is the official upstream release on which `release/2.1.1-4.4`
+* `tinyos/2.1.1` is the official upstream release on which `release/2.1.1-4.5`
is based, the difference being the TMI enhancements.
-* `patchset/2.1.1-4.4` is the head of a string of commits from the
+* `patchset/2.1.1-4.5` is the head of a string of commits from the
`tinyos/2.1.1` tag that represent a clean patch series that applies the
TMI enhancements to the official upstream release.
The official TinyOS installs the source tree at `/opt/tinyos-2.x`. The TMI
version installs source trees at `/opt/tinyos/VER`. For example, the latest
-TMI tree is installed at `/opt/tinyos/2.1.1-4.4`. TMI also maintains in its
+TMI tree is installed at `/opt/tinyos/2.1.1-4.5`. TMI also maintains in its
repository the last few official source trees. At least one must be installed,
and the developer may install others as needed. When installing or upgrading
TMI TinyOS packages via APT, the latest TMI tree package is automatically
to use. This script also updates your shell rc file (if running bash, ksh or
csh) so that your tree selection is persistent across logins.
+Another option is to check out a TinyOS source tree at another location,
+preferably in a user-private directory. This would allow development within the
+TinyOS source in a saner manner than modifying a 'released' tree found in /opt/.
+The tinyos.sh script in the TMI tinyos package also supports this capability.
+
This is the currently available trees as of this writing. You can use the
command shown below to at any time view the available source trees.
- $ sudo apt-cache search tinyos-source
+ $ apt-cache search tinyos-source
tinyos-source - TinyOS source meta package
- tinyos-source-2.0.1 - TinyOS source code tree
- tinyos-source-2.0.2.2 - TinyOS source code tree
- tinyos-source-2.1.0 - TinyOS source code tree, upstream release_2_1_0_0
+ tinyos-source-2.0.1 - TinyOS source code tree, upstream release
+ tinyos-source-2.0.2.2 - TinyOS source code tree, upstream release
+ tinyos-source-2.1.0 - TinyOS source code tree, upstream release
tinyos-source-2.1.0-3 - TinyOS source code tree
tinyos-source-2.1.0-4 - TinyOS source code tree
tinyos-source-2.1.0-4.1 - TinyOS source code tree
- tinyos-source-2.1.1 - TinyOS source code tree, upstream release_2_1_1_3
+ tinyos-source-2.1.0-4.2 - TinyOS source code tree
tinyos-source-2.1.1-4.3 - TinyOS source code tree
tinyos-source-2.1.1-4.4 - TinyOS source code tree
+ tinyos-source-2.1.1-4.5 - TinyOS source code tree
+
+TMI quit providing pristine packages after 2.1.0. Using any TinyOS source tree
+not provided by TMI packages is easy. Simply source the `/opt/tinyos/tinyos.sh`
+script with an argument of the directory containing the source tree.
# Installing TinyOS
projects / oss-web.git / blobdiff