Joyride: Difference between revisions
m (Added a link to the page containing installation information) |
(link to Friends in testing instead of Taking a Joyride, fix headings, explain what Joyride is) |
||
| Line 1: | Line 1: | ||
<center>''For information on helping to |
<center>''For information on helping to test joyride, see [[Friends in testing]]''</center> |
||
= Install joyride = |
== Install joyride == |
||
For information on how to install joyride, |
For information on how to install joyride, see [[Taking a Joyride]]. |
||
= Info = |
== Info == |
||
[[joyride]] is the build stream where bleeding edge development happens. Components from joyride are 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] |
||
= Build process = |
== 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. |
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. |
||
| Line 18: | Line 18: | ||
For information about the software used to build the stream, see [[Build system]]. |
For information about the software used to build the stream, see [[Build system]]. |
||
= Getting packages included = |
== Getting packages included == |
||
== Packages with OLPC-3 disttags == |
=== 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. |
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 == |
=== 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). |
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). |
||
| Line 30: | Line 30: | ||
To make the package land sooner, you can also tag it in <tt>dist-olpc3</tt> |
To make the package land sooner, you can also tag it in <tt>dist-olpc3</tt> |
||
== Local code == |
=== Local code === |
||
For non-koji packages, there is also a dropbox system described in [[Build_system#Instructions_for_Use]]. |
For non-koji packages, there is also a dropbox system described in [[Build_system#Instructions_for_Use]]. |
||
== Kernel == |
=== 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/ |
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/ |
||
Revision as of 09:46, 16 August 2008
Install joyride
For information on how to install joyride, see Taking a Joyride.
Info
joyride is the build stream where bleeding edge development happens. Components from joyride are later pulled into stable branches for release.
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.