Joyride: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
Line 1: Line 1:
<big><font color=red>'''Joyride has been discontinued. Refer to the processes outlined on [[Release Process Home]] to determine where modern-day development builds can be found.'''</font></big>
== Info ==


{{Dated}}
[[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 was a build stream of [[OS images]] where bleeding edge development happened, from an earlier era of OLPC software development. Components from joyride were later pulled into stable branches for release.


* [http://dev.laptop.org/~bert/joyride-pkgs.html ChangeLog]
* [http://dev.laptop.org/~bert/joyride-pkgs.html ChangeLog]
* [http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/ Build downloads]
* [http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/ Build downloads]

=== 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.

<!-- 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
=== Testing ===
For information on helping to test joyride, see [[Friends in testing]].
-->

=== 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 <tt>testing</tt>, and then issue an update to <tt>updates</tt>. This can be done through the web interface at https://admin.fedoraproject.org/updates or through the build checkout: <tt>make update</tt> (you want type=E request=T).

To make the package land sooner, you can also tag it in <tt>dist-olpc3</tt>

=== 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 <tt>/home/dilinger/public_rpms/joyride</tt> on dev.laptop.org. The joyride build system then automatically notices the new kernel RPMs and includes them in the next build.


[[Category:Builds]]
[[Category:Builds]]

Revision as of 15:18, 7 February 2011

Joyride has been discontinued. Refer to the processes outlined on Release Process Home to determine where modern-day development builds can be found.


Emblem-warning.png The currency of this article or section may be limited by out-of-date information.
There may be relevant discussion on its talk page

Joyride was a build stream of OS images where bleeding edge development happened, from an earlier era of OLPC software development. Components from joyride were later pulled into stable branches for release.