[Tinyos-2.0wg] Re: tinyos-2-0-0-beta2-candidate

[Vlado Handziski]

On 7/3/06, Philip Levis <pal at cs.stanford.edu> wrote:
>
> On Jun 30, 2006, at 3:42 PM, David Gay wrote:
>
> >
> > - At some point (not for the beta2) we should make a new tinyos-tools
> > rpm (there's at least one semi-important fix to ncc, related to
> > sensorboards and include directory searching)
>
>
> I think that we need a new tools RPM; there are changes in ncc for
> TOSSIM since 1.2.3.
>
> Phil
>

What about a new tinyos RPM with the remaining testing apps? I have finished
the testing of the current RPM on eyesIFX and everything seems OK, apart
from the Sense applications output (showing MSB vs. LSB bits). I have only
tested on Linux, I don't have the msp430 tools for cygwin.


Here are some general issues with the current RPMs. Some of the notes are
for post-beta consideration. Testing has been done on a clean Fedora Core 5
installation running in VMware.

[tester at localhost download]$ sudo rpm -ivh nesc-1.2.7-1.i386.rpm
error: Failed dependencies:
        /usr/bin/guile is needed by nesc-1.2.7-1.i386
[tester at localhost download]$

Is schema really needed for runtime use of nesc? It is not installed by
default on FC5, so this should be listed in the documentation. To handle
gracefully we migh sugest the use of yum:

------------------------------
sudo yum install nesc-1.2.7-1.i386.rpm
...

Dependencies Resolved

=============================================================================
 Package                 Arch       Version          Repository        Size
=============================================================================
Installing:
 nesc                    i386       1.2.7-1          nesc-1.2.7-1.i386.rpm
1.5 M
Installing for dependencies:
 guile                   i386       5:1.6.7-6        core              1.2 M
 slib                    noarch     3a1-5.1          core              805 k

Transaction Summary
=============================================================================
Install      3 Package(s)
Update       0 Package(s)
Remove       0 Package(s)
Total download size: 3.4 M
Is this ok [y/N]:

Package nesc-1.2.7-1.i386.rpm is not signed

but as you can see, for this we need to sign the RPM, since by default yum
does not install unsigned packages.


------------------------------

TinyOS RPM:

[tester at localhost download]$ sudo rpm -ivh tinyos-2.0.0beta2-1.noarch.rpm
error: Failed dependencies:
        perl(GraphViz) is needed by tinyos-2.0.0beta2-1.noarch

This has been reported before. There is no "official" RPM package on FC5
satisfying this dependency.


------------------------------

MSP430:

Are we going to provide our own msp430 toolchain RPMs ?


------------------------------
General:

While I understand the benefits of having common .spec files for cygwin and
linux, I think that we are ending up with packages that do not provide
"turn-key" solution on linux and can confuse a lot of early users. The main
problems that I see are:

- the packages are not fully relocatable with  --prefix. I think that by
default we should install all binaries in /opt and use /etc/profile.d/xxx.sh
/etc/profile.d/xxx.tcsh to amend the paths.

- the packages are not properly setting the permissions to the serial
devices and the ownership of the /opt/tinyos-2.x files is left to be
root.root

We have solved all of the issues above in our eyesIFX installer kit:

https://wg.tkn.tu-berlin.de/twiki/bin/view/WSN/EyesIFXDevelopmentKitSoftwarePackageInstallation

(the .spec files and the separate RPMs on the wiki are not the latest
versions, I will fix this tomorrow. The GEKSI archive is current though)

If we decide to provide separate linux and windows RPMs, we can reuse the
solutions from the kit to provide "turn-key" RPM packages that provide all
the necessary setup on FC.

------------------------------
App makefiles:

By creating the java and python message files by default we are introducing
a large dependency for the users that don't wand any PC support. They should
be created on demand or we should add "detection logic" and build only the
message stubs for the language that the user has installed or has selected
as option during the installation of the RPMs.

Also, please consider using a variable for the java compiler in the
Makefiles. In many cases we need to change JAVAC=gcj -C to get gcc-java
support. The only thing currently not working with gcj is the Oscilloscope
application because of missing widgets.



Vlado
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.millennium.berkeley.edu/pipermail/tinyos-2.0wg/attachments/20060704/7d6ca8ae/attachment.html