Difference between revisions of "Automate Pidora Kernel"

From CDOT Wiki
Jump to: navigation, search
Line 47: Line 47:
 
<!-- Note: Each student must have unique goals. These goals may be ''related'' to other students' work, but must be ''distinct'' and ''attainable'' regardless of the state of the other students' work. For example, under the umbrella of one project title, one student may work on packaging a piece of software and another may work on documentation, or one may work on solving one bug and another on solving another bug, but two students must not work on the same bug or depend on the other students' work in order to be able to complete their own project. -->
 
<!-- Note: Each student must have unique goals. These goals may be ''related'' to other students' work, but must be ''distinct'' and ''attainable'' regardless of the state of the other students' work. For example, under the umbrella of one project title, one student may work on packaging a piece of software and another may work on documentation, or one may work on solving one bug and another on solving another bug, but two students must not work on the same bug or depend on the other students' work in order to be able to complete their own project. -->
 
* 0.1 Prototype build in either python or bash able to retrieve package from github and send it to koji
 
* 0.1 Prototype build in either python or bash able to retrieve package from github and send it to koji
* 0.2 Finish code, add options if I find they could be helpful in some way. Comment code and do lots of testing.  
+
* 0.2 Finish code, add options if I find they could be helpful in some way. Extra comments and testing for bugs.  
 
* 0.3 Create man page, perform tweaks and send for release.
 
* 0.3 Create man page, perform tweaks and send for release.
  

Revision as of 09:43, 17 October 2013

Automate Pidora Kernel and Firmware Building

Project Description

The Raspberry Pi Foundation maintains a kernel fork that is updated frequently. We would like to package kernel and firmware changes on a daily basis, and have these available in a testing repository so that anyone can use them. Periodically, we will select a kernel-firmware combination from this testing repository and make it available as the main Pidora kernel.

Project Leader

Ronald Hernandez


Project Contributor(s)

Project Details

Use Python or Bash to create a script that will be automate the process of compiling the newest kernel. This will be done by checking Github for the latest kernel, downloading it, updating the spec file and sending the build to koji. This build will stay in a testing repository.

Project Plan

Tracking

Progress can be tracked in my Blog

Key contacts

Chris Tyler, Andrew Green (soon)

Goals by Release

Goals for each release and plans for reaching those goals:

  • 0.1 Prototype build in either python or bash able to retrieve package from github and send it to koji
  • 0.2 Finish code, add options if I find they could be helpful in some way. Extra comments and testing for bugs.
  • 0.3 Create man page, perform tweaks and send for release.

Communication

Email: rhernandez2@myseneca.ca IRC: rhernandez2

Mailing Lists

fedora fedora-devel fedora-arm


Upsteam Wiki and Web

Links/Bugs/Tracking

Source Code Control

Blogs

Non-Seneca Participants

Planets

Project News