Builds and release process

C. Scott Ananian cscott at
Sat Dec 15 12:32:01 EST 2007

On Dec 15, 2007 11:52 AM, Michael Stone <michael at> wrote:
> Scott has written very detailed instructions on how to do this but his
> documentation is currently located on the internalwiki in pursuit of, in
> my view, security by obscurity. Since I am not maintaining these
> servers, I do not wish to contradict his choice by publishing the
> contents of the server configuration pages; however, you might chat with
> him about ways that he would feel comfortable making this information
> more broadly visible.

Michael, you're grossly mischaracterizing -- and being unhelpful to boot.

Michael wrote a very useful README.olpc in the pilgrim source tree
which describes how to set up pilgrim.  The only details on the
internalwiki are machine-specific configuration which will not be
useful to you.  Patches to README.olpc are always welcome.  The only
thing you really need is the pointer to git:

The 'master' branch is generally what you need; there are separate
branches for (again) machine-specific configuration (the 'autobuild'
branch covers integration of pilgrim with our joyride build system,
which is constantly changing).  Sometimes branch-specific changes
creep into (say) the ship.2 build which aren't in master; I try to
avoid that whenever possible.  Contributions to pilgrim should be made
against the master branch.

All this said, I really think that running your own pilgrim instance
will only slow down your development process unless you are (like
marco and bernie) responsible for a large number of inter-related
packages.  In general, RPM installing your modified packages on top of
the latest joyride build is the recommended development process --
it's a lot faster!

                         ( )

More information about the Devel mailing list