View source for Change raspberrypi-vc Package to Build from Source Project

<!--





#### EDIT A COPY OF THIS PAGE, NOT THE ORIGINAL SAMPLE PROJECT PAGE! ####





-->

= Change raspberrypi-vc Package to Build from Source =
<!-- Replace "Project Name" with the actual name of the project in the line above. -->

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

[http://zenit.senecac.on.ca/wiki/index.php/User:Jose_Francisco_Gonzales_Giagonia Jose Giagonia]


== Project Contributor(s) ==

<!-- Name(s) of people casually working on the project, or who have contributed significant help.  Include links to personal pages within wiki. Adding the names of your contributors here is a nice way to thank them.

NOTE: only the Project Leader should add names here.  You should not add your own name to the Contributor list. -->

== Project Details ==

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

<!-- Provides more depth than the Project Description.  This is the place for technical discussions, project specs, or other details.  If this gets very long, you might consider breaking this part into multiple pages and linking to them. -->

== 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 ===
<!-- Describe the tracking mechanisms you are using for your project (bugzilla, trac, github, ...) -->

=== Key contacts ===
<!-- Add links to any mentors or key participants in the community. -->

=== Goals by Release ===

Goals for each release and plans for reaching those goals:
<!-- 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 

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 ===
<!-- Add any appropriate mailing lists to which you are subscribed (e.g., see http://lists.fedoraproject.org -->

=== Upsteam Wiki and Web ===
<!-- Links to upstream wiki/web pages -->

=== Links/Bugs/Tracking ===
<!-- Add a link to any page(s) related to your work, including the bug numbers (on bugzilla or trac) -->

=== Source Code Control ===
<!-- Add a link to source code URLs, including git/mercurial/svn/cvs repositories -->

=== Blogs ===
<!-- Links to the blogs of people involved, both inside and outside Seneca -->

=== Non-Seneca Participants ===
<!-- Links to the blogs of any non-Seneca participants in this project -->

=== Planets ===
<!-- Links to any planets related to this project -->

== Project News ==

<!-- This is where a permanent record of your releases and updates will go.  In these you should discuss the status or your work, your interactions with other members of the community (e.g., Seneca and Mozilla), problems you have encountered, etc. -->