Joyride: Difference between revisions
(→Info: add a section "Joyride is not producing usable releases" and hide Testing section.) |
(→Joyride is not producing usable releases: improve phrasing) |
||
| Line 9: | Line 9: | ||
OLPC is transitioning to running a stock Linux distribution that will run Sugar as an application. See [[Future releases]] for more details. |
OLPC is transitioning to running a stock Linux distribution that will run Sugar as an application. See [[Future releases]] for more details. |
||
Although the automated Joyride machinery still creates Joyride builds |
Although the automated Joyride machinery still creates Joyride builds that pull in updated packages, as of February 2009 it is not being maintained and engineers do not recommend it. ''Eventually'' the equivalent of "joyride" will be development builds of the various Linux distributions that have been turned into XO-1 images. |
||
<!-- This testing section is invisible (turned into an HTML comment), as neither Friends_in_testing page nor cjb recommend testing joyride. -- User:Skierpage on 2009-02-23 |
<!-- This testing section is invisible (turned into an HTML comment), as neither Friends_in_testing page nor cjb recommend testing joyride. -- User:Skierpage on 2009-02-23 |
||
| Line 15: | Line 15: | ||
For information on helping to test joyride, see [[Friends in testing]]. |
For information on helping to test joyride, see [[Friends in testing]]. |
||
--> |
--> |
||
=== Install joyride === |
=== Install joyride === |
||
Revision as of 02:20, 25 February 2009
Info
joyride is the build stream of OS images where bleeding edge development happens. Components from joyride are later pulled into stable branches for release.
Joyride is not producing usable releases
OLPC is transitioning to running a stock Linux distribution that will run Sugar as an application. See Future releases for more details.
Although the automated Joyride machinery still creates Joyride builds that pull in updated packages, as of February 2009 it is not being maintained and engineers do not recommend it. Eventually the equivalent of "joyride" will be development builds of the various Linux distributions that have been turned into XO-1 images.
Install joyride
For information on how to install joyride, see Taking a Joyride.
Build process
Joyride releases are built automatically. A cronjob runs the build scripts 4 times every day. The build script checks for new/updated packages (aborting if there is nothing to do). After a new build has been made, it is announced on the devel mailing list.
For information about the software used to build the stream, see Build system.
Getting packages included
Packages with OLPC-3 disttags
If the package in question has an OLPC-3 branch, simply building under that branch will result in joyride inclusion. Just run "make build" from the OLPC-3 directory.
Packages without OLPC-3 disttags
For other packages, e.g. ones that go to Fedora 9 disttags (F-9), you must issue an update to testing, and then issue an update to updates. This can be done through the web interface at https://admin.fedoraproject.org/updates or through the build checkout: make update (you want type=E request=T).
To make the package land sooner, you can also tag it in dist-olpc3
Local code
For non-koji packages, there is also a dropbox system described in Build_system#Instructions_for_Use.
Kernel
Joyride currently uses the "testing" branch of the olpc-2.6 kernel git repository. RPMs of this kernel are built nightly and published at http://dev.laptop.org/~dilinger/testing/
When we want to include a kernel update in Joyride, Andres Solomon (dilinger) manually takes the RPMs as above and puts them in /home/dilinger/public_rpms/joyride on dev.laptop.org. The joyride build system then automatically notices the new kernel RPMs and includes them in the next build.