Open main menu

CDOT Wiki β

Changes

Fall 2011 SBR600 Weekly Schedule

89 bytes added, 13:06, 16 September 2011
no edit summary
== Friday ==
 
 
=== 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.
=== Project Selection ===
** Release 0.3: Completed working state - The work is complete and documented. Any upstream review, whether formal or informal, has been completed, feedback has been incorporated into the project, and the work has been committed been
* You must have a strategy in place for reaching your targets.
You will make a brief (3-5 minute) presentation of your project plans on '''ThursdayTuesday, February 3September 27'''.  === Resources ===* mock** [[:fedora:Projects/Mock|Mock Project page]]** [[:fedora:Using_Mock_to_test_package_builds|Using Mock to test package builds]]
=== ToDo ===
* Finish [[SBR600 RPM-Writing Lab|building your two RPMs]] by Monday, September 19 (we'll use them in the next lab)- '''remember to blog!'''
* Send your [[SSH]] key to [[User:Chris Tyler|your prof]] by Monday, September 19 (also needed for the next lab)
* Review the [[SBR600 Potential Projects]] and start researching the top 2-3 possibilities.
== Thursday ==
=== mock: Testing BuildRequires ==Week 3 (September 19) - Koji and Solving Build Issues =
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.== Tuesday ==
=== koji: Testing multiple architectures ===
<code>koji</code> is a client-server system which allows you to queue builds within the Fedora build farm. This permits you to test whether your package builds on several different architectures, which is especially useful when you don't otherwise have access to the machines of that architecture.
 
=== Solving Build Issues ===
 
* Reasons for Build Failures
* Solving Build Failures
=== Resources ===
* mock
** [[:fedora:Projects/Mock|Mock Project page]]
** [[:fedora:Using_Mock_to_test_package_builds|Using Mock to test package builds]]
* koji
** [[:fedora:PackageMaintainers/UsingKoji|Using Koji]]
 
=== ToDo ===
* [[SBR600 Mock and Koji Lab|Mock and Koji Lab]]
= Week 3 (September 19) - Solving Build Issues =
 
* Reasons for Build Failures
* Solving Build Failures
= Week 4 (September 26) - Project Plan Presentations =