Pilgrim: Difference between revisions

From OLPC
Jump to navigation Jump to search
m (explicitly use category over template)
(Link to other related information.)
Line 1: Line 1:
{{Software}}
{{Software}}

More information on pilgrim is at [[Building custom images]].


=== Pilgrim ===
=== Pilgrim ===

Revision as of 18:11, 29 July 2008


More information on pilgrim is at Building custom images.

Pilgrim

Please add text to answer the following questions:

  • what is Pilgrim?
  • is it already on XO laptops or do you need to install it?
  • What problem does it solve?
  • Who is expected to use it?
  • What are the typical use cases for Pilgrim?

Details

Source code

Pilgrim is composed of two large and two small scripts and many configuration files.

 pilgrim              # user-interface
 pilgrim-autobuild    # implementation
 build-one            # build the current branch
 make-repos           # touch up yum repositories

The most important branch is "autobuild". This is where changes deemed suitable for all build branches should be merged. See Pilgrim Commit Policy.

The other branches - joyride, meshtest, xtest, and rainbow store branch-specific data like which yum repositories to compose into the image, which packages to pull, which activities to include, and so on.


These data are mostly recorded in

 streams.d/olpc-branch.conf                    # a few important config variables
 streams.d/olpc-development-yum-install.conf   # yum repositories to compose, package exclusions
 streams.d/olpc-development.stream             # lists of packages and activities to install

Questions:

  • How do you enumerate the available branches? I.e. if you don't want to rely on the documentation being kept up to date...
  • Where can one find the streams.d directory?