Difference between revisions of "Change raspberrypi-vc Package to Build from Source Project"

From CDOT Wiki
Jump to: navigation, search
(Project Plan)
 
Line 41: Line 41:
  
 
1. Take a look at the existing raspberrypi-vc package to see how it works. Notice that it uses a tarball containing prebuilt programs instead of the source code.
 
1. Take a look at the existing raspberrypi-vc package to see how it works. Notice that it uses a tarball containing prebuilt programs instead of the source code.
 +
 
2. Experiment with a direct from-source build of the raspberrypi-vc code (forget about RPMs at first). Make sure you understand the build process well.
 
2. Experiment with a direct from-source build of the raspberrypi-vc code (forget about RPMs at first). Make sure you understand the build process well.
 +
 
3. Modify the raspberrypi-vc package to build from source instead of using the prebuilt binaries.
 
3. Modify the raspberrypi-vc package to build from source instead of using the prebuilt binaries.
  

Latest revision as of 18:34, 4 November 2013


Change raspberrypi-vc Package to Build from Source

Project Description

The raspberry-vc package are not built with the same options as the rest of the Pidora packages. This project aims to compile and package a new version of the raspberry-vc package which would be built on source and will be ompatible with the current Pidora package.

Project Leader

Jose Giagonia


Project Contributor(s)

Project Details

The raspberry-pi-vc package uses pre-built binaries from the Raspberry Pi Foundation.


Project Plan

1. Take a look at the existing raspberrypi-vc package to see how it works. Notice that it uses a tarball containing prebuilt programs instead of the source code.

2. Experiment with a direct from-source build of the raspberrypi-vc code (forget about RPMs at first). Make sure you understand the build process well.

3. Modify the raspberrypi-vc package to build from source instead of using the prebuilt binaries.


Tracking

Key contacts

Goals by Release

Goals for each release and plans for reaching those goals:

  • 0.1

1. Learn the package.

  * It's purpose.
  * What is inside.
  * Source code checking.

2. Contacts

  * Use IRC and the Pidora community to ask questions.
  * Talk to people at CDOT to answer some questions.

3. Test

  * Test the package on Pidora.
  * Make it build on source.
  * Try to send it for review.
  • 0.2

1. Fix

  * Fix any issues
  * Test Again
  

2.

  • 0.3

1. Final test

  * 'A new version of the raspberrypi-vc package that build from source, is compatible with the current Pidora package, and can be easily updated/maintained'

Communication

Mailing Lists

Upsteam Wiki and Web

Links/Bugs/Tracking

Source Code Control

Blogs

Non-Seneca Participants

Planets

Project News