Home · Support · Download · Hardware Designs · Projects · Pubs

TinyOS FAQ
Join/Search Mailing Lists
Documentation

TinyOS Site

WWW

 I want to search the TinyOS Mail Archives

If you have any questions about or additions to these instructions, please send mail to Kristin.

How to commit your minitask software to the TinyOS CVS repository

For more information on CVS, use the info utility as in ‘info cvs’. I believe the info utility is available on all recent Unix machines.

Start by gaining access to the repository:

  1. If you don’t have one already, create a SourceForge username. You can do that here: https://sourceforge.net/account/register.php
     
  2. Send email to Kristin requesting Developer Access to the CVS tree. Include your SourceForge username in the email. (Note: any TinyOS group member can probably do this, but emailing Kristin might be the quickest route.)

Once you have Developer access to the repository, you can create your directory. The convention is to commit your software under minitasks/02/<your-institution>.

  1. Check out the current minitasks CVS tree. There are instructions for doing this at https://sourceforge.net/cvs/?group_id=28656. Here’s how I would do it.

    $cvs export CVS_RSH=ssh
    $cvs -z3 -d:ext:kristinwright@cvs.sourceforge.net:/cvsroot/tinyos co minitasks

    You will end up with the CVS tree rooted at minitasks. Note that in all these cvs commands, you’ll be asked for your sourceforge password.
     
  2. Add your own directory structure. To add, for example, ‘uva’, use the CVS command ‘cvs add’. I would do the following:

    $cd minitasks/02
    $mkdir uva
    $cvs add uva
     
  3. Add your own source files. Consider the long-term picture: you may want another subdir under your institution name.

    If I wanted to add ‘route.nc’ and ‘test.nc’ to CVS I would do the following (remember that the files must exist):

    $ cvs add route.nc test.nc
    $ cvs commit -m “first pass; compiles but missing functionality” route.nc test.nc
     
  4.  


Home | Download | Support | Publications | Hardware Designs | Related Work | Internal

This project is part of Berkeley WEBS: Wireless Embedded Systems