Difference between revisions of "Fall 2011 SBR600 Weekly Schedule"
Chris Tyler (talk | contribs) |
Chris Tyler (talk | contribs) |
||
Line 29: | Line 29: | ||
# [[SBR600 Fedora Installation|Fedora Installation]] | # [[SBR600 Fedora Installation|Fedora Installation]] | ||
+ | = Week 2 - Jan 17 = | ||
+ | |||
+ | = Tuesday == | ||
+ | |||
+ | === Using ''make'' === | ||
+ | |||
+ | * [[SBR600 make and Makefiles|make and Makefiles]] | ||
+ | |||
+ | === Building from Source === | ||
+ | |||
+ | * Obtaining source code | ||
+ | * Configuring the build | ||
+ | * Performing the build | ||
+ | * Testing the build | ||
+ | * Installing the built software | ||
+ | |||
+ | ==== RPM Packages ==== | ||
+ | |||
+ | * Differences between managing RPMS and Installing from Source | ||
+ | ** RPMS provide a database of installed software | ||
+ | *** Let you determine what's installed | ||
+ | *** Automatic management of dependencies | ||
+ | *** Identify the origin of files | ||
+ | *** Permit easy update or removal | ||
+ | *** Enable you to verify installation (useful for spotting file corruption and intrusions) | ||
+ | * [[RPM Package Contents|Contents of an RPM Package]] | ||
+ | |||
+ | ==== The RPM Database ==== | ||
+ | |||
+ | * [[RPM Queries|Querying the RPM database]] | ||
+ | |||
+ | ==== Creating an RPM Package ==== | ||
+ | * [[RPM Packaging Process]] | ||
+ | |||
+ | ==== Resources ==== | ||
+ | |||
+ | * Two simple [http://matrix.senecac.on.ca/~chris.tyler/osd600/makefile-examples.tgz makefile examples] | ||
+ | * [[:fedora:PackageMaintainers|Fedora Package Maintainers page]] | ||
+ | ** [[:fedora:PackageMaintainers/CreatingPackageHowTo|Packaging How-To]] | ||
+ | * ''Fedora Linux'' chapter 5 (see Seneca Library website > eBooks > View All > Safari > Fedora Linux). | ||
+ | * rpmlint | ||
+ | ** [[:fedora:Common Rpmlint issues|Fedora Common Rpmlint issues]] | ||
+ | |||
+ | === To Do === | ||
+ | |||
+ | By '''Thursday, January 19''': | ||
+ | # [[SBR600 Build-from-Source Lab|Build-from-Source Lab]] | ||
+ | # [[SBR600 RPM-Writing Lab|RPM-Writing Lab]] | ||
+ | # Send your [[SSH]] public key to [[User:Chris Tyler|your professor]] so he can create accounts for you on the [[CDOT Development Systems]]. | ||
<!-- | <!-- |
Revision as of 09:22, 17 January 2012
Previous semester: Fall 2011 SBR600 Weekly Schedule
Contents
Week 1 (Jan 10) - Introduction
Tuesday
Welcome
- About this course
- Introductions
Intro to SBR600 - Software Build & Release
- Brief overview of the Build & Release process
- Introduction to the Fedora Project
- Fedora Project
- Fedora ARM Secondary Architecture project at Seneca and at the Fedora Project
- Course Layout
- Project-based course
- Working with Open Source
- Working with the Fedora Project
- Course Outline
- How this Course Works
- SBR600 Communication Tools
- How coursework is submitted in SBR600
To Do
By Tuesday, January 17:
Week 2 - Jan 17
Tuesday =
Using make
Building from Source
- Obtaining source code
- Configuring the build
- Performing the build
- Testing the build
- Installing the built software
RPM Packages
- Differences between managing RPMS and Installing from Source
- RPMS provide a database of installed software
- Let you determine what's installed
- Automatic management of dependencies
- Identify the origin of files
- Permit easy update or removal
- Enable you to verify installation (useful for spotting file corruption and intrusions)
- RPMS provide a database of installed software
- Contents of an RPM Package
The RPM Database
Creating an RPM Package
Resources
- Two simple makefile examples
- Fedora Package Maintainers page
- Fedora Linux chapter 5 (see Seneca Library website > eBooks > View All > Safari > Fedora Linux).
- rpmlint
To Do
By Thursday, January 19:
- Build-from-Source Lab
- RPM-Writing Lab
- Send your SSH public key to your professor so he can create accounts for you on the CDOT Development Systems.