Open main menu

CDOT Wiki β

Changes

Fall 2012 DPI908/SBR600 Weekly Schedule

143 bytes added, 20:35, 4 September 2012
no edit summary
Previous semester: [[Winter 2012 SBR600 Weekly Schedule]]
<!-- ---------------------------------------------------------------------------------------------- Week 1 ------------ -->
= Week 1 (September 3) - Introduction =
== Wednesday ==
** How coursework is submitted
* Differences between [[DPI908]] and [[SBR600]]
* Future
** Winter 2013 Semester
*** Project continuation course
** Upcoming Events
*** [http://fsoss.ca Free Software and Open Source Symposium 2012]
*** [[:fedora:FUDCon:Lawrence_2013|FUDCon Lawrence 2013]]
=== To Do ===
 
'''By Monday, September 10:'''
# [[DPI908/SBR600 Communication Lab|Communication Lab]]
# [[DPI908/SBR600 Fedora Installation|Fedora Installation]]
<!-- ---------------------------------------------------------------------------------------------- Week 2 ------------ -->= Week 2 (September 10) - Building from Source, RPM Packaging, Mock, and Koji =
== Monday ==
By '''Wednesday, September 12''':
# [[DPI908/SBR600 Build-from-Source Lab|Build-from-Source Lab]]
# Send your [[SSH]] public key to [[User:Chris Tyler|your professor]] professors so he they can create accounts for you on the [[CDOT Development Systems]].
{{Admon/note|Edited to this point|}}
== Thursday Wednesday == 
==== Creating an RPM Package ====
 
* [[RPM Packaging Process]]
# [[DPI908/SBR600 RPM-Writing Lab|RPM-Writing Lab]]
 
 
=== Mock: Testing BuildRequires ===
 
It's often difficult to get the BuildRequires in a spec file exactly right, because it's easy to overlook packages that are coincidentally installed on the machine. ''Mock'' is used to test that the BuildRequires for a package are complete and accurate, by creating a bare-bones [http://en.wikipedia.org/wiki/Chroot chroot] environment containing only the [[:fedora:Packaging/Guidelines#Exceptions_2|basic build packages]] plus any packages indicated by BuildRequires lines in the spec file.
 
=== Koji: Testing on Multiple Architectures ===
 
Most developers and packagers have access to only a small number of system architectures (for example, a developer might have access to 64-bit AMD/Intel, but not have access to 32-bit AMD/Intel, s390 mainframe, PowerPC, or ARM systems). The ''Koji'' build system provides a mechanism for building a package in mock on one or more remote systems.
=== To Do ===
By '''Tuesday, January 24''':
# * [[DPI908/SBR600 Mock and Koji RPM-Writing Lab|RPM-Writing Lab]]
<!-- ---------------------------------------------------------------------------------------------- Week 3 ------------ -->
= Week 3 (Jan 24) - The Fedora Build System =
# [[SBR600 Mock and Koji Lab]]
== Tuesday ==
* Work on packages
<!-- ---------------------------------------------------------------------------------------------- Week 4 ------------ -->
= Week 4 (Jan 31) =
You will make a brief (3-5 minute) presentation of your project plans on '''Thursday, February 9'''.
<!-- ---------------------------------------------------------------------------------------------- Week 5 ------------ -->
= Week 5 (Feb 7) =
** Challenges and potential pitfalls that you have identified, and your approach to mitigating those challenges so that you can complete your project on time regardless of things beyond your control.
** Time for a brief Q&A/Feedback session at the end.
 
<!-- ---------------------------------------------------------------------------------------------- Week 6 ------------ -->
= Week 6 (Feb 14) =
* Blog about your experience.
<!-- ---------------------------------------------------------------------------------------------- Week 7 ------------ -->
= Week 7 (Feb 21) =