Taste the Rainbow:0.7.0: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
m (Taste the Rainbow moved to Taste the Rainbow:0.7.0: Rainbow 0.7.2 needs to be documented.)
 
(8 intermediate revisions by the same user not shown)
Line 3: Line 3:
== Source Code Overview ==
== Source Code Overview ==
please start at http://dev.laptop.org/git?p=users/mstone/security;a=tree;f=rainbow;h=b76a41fcc968b22196b14fa868e50db0f4b1b9bc;hb=b6a2a0c96f522956a69871c6d839bc67d2f78424
Please start in my [http://dev.laptop.org/git?p=users/mstone/security;a=tree;f=rainbow;h=b76a41fcc968b22196b14fa868e50db0f4b1b9bc;hb=b6a2a0c96f522956a69871c6d839bc67d2f78424 rainbow-0.7.0 tree].


./rainbow

|--- README : Standard boilerplate about where work gets done; somewhat dated in this release.
rainbow
|--- conf : installation-time configuration files
|--- conf : installation-time configuration files
| \--- session-olpc.conf : applies some unusual dbus rules to allow many uids
| \--- session-olpc.conf : applies some unusual dbus rules to allow many uids
Line 14: Line 14:
|
|
|--- docs : explanations & notes
|--- docs : explanations & notes
| |--- DESIGN : A discussion of how the predecessor to the current architecture arose.
| |--- README
| \--- NOTES : various problems I have encountered and thoughts on how to solve them.
| \--- DESIGN
| *--- [http://dev.laptop.org/git?p=security;a=blob;f=rainbow.txt;hb=HEAD rainbow.txt]
| *--- [http://dev.laptop.org/git?p=security;a=blob;f=rainbow.txt;hb=HEAD rainbow.txt] : a sketch & justification of the current design
|
|
|--- rainbow : source code
\--- rainbow : source code
|--- permissions : a stub based on the secure installation work that marcopg and
| |--- util
| neuralis did together a few weeks ago
| |--- stages
|--- util : functions wrapping frequently used idioms or useful syscalls
| |--- targets
|--- stages : logic implementing activity launching
| \--- service.py
|--- targets : control flow describing how to call activity-launching code
|
\--- service.py : dbus service entry-point
|--- rainbow.spec.in : spec-file template for building RPMS
\--- Makefile.package : package-specific variables for use in ../Makefile.fedora
./rainbow.spec.in : spec-file template for building RPMS
*--- ../Makefile.fedora : rules for making local snapshot builds and
./Makefile.package : package-specific variables for use in ../Makefile.fedora
internal releases, prior to pushing to Fedora
../Makefile.fedora : rules for making local snapshot builds and
internal releases, prior to pushing to Fedora


== Activity Launching ==

== Features ==

=== Activity Installation ===

permissions is a stub that I hope to fill out this weekend based on the secure installation work that marcopg and neuralis did together a few weeks ago

=== Activity Launching ===


The key functions for launching activities are
The key functions for launching activities are
Line 51: Line 46:


These six functions (and the relatively simple helpers they call) exhaust the functionality provided by rainbow-0.7.0.
These six functions (and the relatively simple helpers they call) exhaust the functionality provided by rainbow-0.7.0.

== Developing Rainbow ==

I develop Rainbow in four basic modes:

* From a live git clone, when developing new features.
cp setup.py.in setup.py
sed -i -e 's/@VERSION@/1/' setup.py
python setup.py develop
* By packaging snapshots of a git clone to try out packaging changes.
make snapshot
* With locally-built or scratch-built packages, when I'm getting ready to tag a release.
make release
* With an official release, built with Fedora's Koji build system from sources archived in Fedora CVS.
** [http://fedoraproject.org/wiki/PackageMaintainers/UpdatingPackageHowTo Fedora Package Update HOWTO]

Latest revision as of 19:58, 6 November 2007

This page is a guided tour of the source code of the rainbow-0.7.0 release.

Source Code Overview

Please start in my rainbow-0.7.0 tree.

 ./rainbow
  |--- README : Standard boilerplate about where work gets done; somewhat dated in this release.
  |--- conf : installation-time configuration files
  |     \--- session-olpc.conf : applies some unusual dbus rules to allow many uids
  |                              to use the same session bus and enables OLPC-specific 
  |                              dbus access checks. When /etc/olpc-security exists, 
  |                              session-olpc.conf is loaded by /usr/bin/sugar 
  | 
  |--- docs : explanations & notes
  |     |--- DESIGN : A discussion of how the predecessor to the current architecture arose.
  |     \--- NOTES : various problems I have encountered and thoughts on how to solve them.
  |     *--- rainbow.txt : a sketch & justification of the current design
  |
  \--- rainbow : source code
        |--- permissions : a stub based on the secure installation work that marcopg and 
        |                  neuralis did together a few weeks ago
        |--- util : functions wrapping frequently used idioms or useful syscalls
        |--- stages : logic implementing activity launching
        |--- targets : control flow describing how to call activity-launching code
        \--- service.py : dbus service entry-point
    
 ./rainbow.spec.in : spec-file template for building RPMS
 ./Makefile.package : package-specific variables for use in ../Makefile.fedora
 ../Makefile.fedora : rules for making local snapshot builds and 
                      internal releases, prior to pushing to Fedora

Activity Launching

The key functions for launching activities are

These functions are called in the order listed from

which are, in turn, called from

These six functions (and the relatively simple helpers they call) exhaust the functionality provided by rainbow-0.7.0.

Developing Rainbow

I develop Rainbow in four basic modes:

  • From a live git clone, when developing new features.
 cp setup.py.in setup.py 
 sed -i -e 's/@VERSION@/1/' setup.py 
 python setup.py develop
  • By packaging snapshots of a git clone to try out packaging changes.
 make snapshot
  • With locally-built or scratch-built packages, when I'm getting ready to tag a release.
 make release