Changes

== Resources ==

* [[:fedora:PackageMaintainers |Fedora Package Maintainers page]]** [[:fedora:PackageMaintainers/CreatingPackageHowTo |Packaging How-To]]

See also "Fedora Linux" chapter 8 5 (see Seneca Library website > eBooks > View All > Safari > Fedora Linux).

* Take the software you compiled last week and package it. Blog about the experience. Include a link to your source RPM (and optionally your binary RPM) from your blog.* Remember to blog about your [[LUX Project|project]] work this week.

Andrew Overholt works at Red Hat's Toronto office , primarily focusing on Eclipse; he'll be speaking about packaging issues. This session will be videotaped for the web. '''ToDo:''' * Prepare for the test and presentation next week.** [[SPR720 Midterm Practice]]* Keep on blogging! = Week 7 (Oct 13) - Midterm test Part A and Presentations = == Midterm Test Part A == On Tuesday we'll be doing the multiple-choice portion of the midterm test for this course. == Presentations == A 5-minute presentation about your 0.1 project release (details provided by John Selmys).

= Week 8 (Oct 27) - Using Mock and Creating a Repository = * Key documents:** [[:fedora:PackageMaintainers/Join]] (How to become a Fedora package maintainer. Includes instructions on setting up a packaging environment, using Koji, and more).** [[:fedora:PackageMaintainers/NewPackageProcess]] (Short version of above, intended for existing package maintainers). * Mock is a tool for creating chroot environments and populating them with packages. One of its main uses is to test and verify the <code>BuildRequires</code> values in spec files: mock -r ''configuration-file'' --rebuild ''name-of-srpm'' The <code>configuration-files</code> can be found in <code>/etc/rpm</code> (example: <code>fedora-9-x86_64</code>). * Koji is the Fedora build server system (koji.fedoraproject.org). The same name is used for the Koji software, which you can install on your own build server.** Koji can checkout code from the Fedora CVS and build it. This is usually done under the control of the makefiles created when a CVS module is generated for a new package.** Koji can also be used for a ''scratch build'', where any source RPM is submitted for building. If your packaging environment is set up, you can request a scratch build with a command such as this (where ''ppc'' is the arch, ''dist-f9'' is the build target, and ''nled-2.52-3.fc8.src.rpm'' is the source package):  koji build --arch-override=ppc --scratch dist-f9 nled-2.52-3.fc8.src.rpm '''TODO''':* Do the [[SPR720 Package Review Lab]]* Blog about your project progress, particularly your plans for your 0.2 release (see [[LUX Project]]). = Week 9 (Nov 3) - Python Scripting Basics I Midterm Test part II and Guest Speakers = * Write the second part of the Midterm test* Guest speakers: Tom and Anton = Week 10 (Nov 10) - Python Scripting Basics II I = * Read: Chapters 1-5 in the textbook (available online from the Seneca library website) * Do the [[SPR720 Python Lab I]]** Please complete the lab by ''Monday'' = Week 11 (Nov 17) - Python Scripting Basics II and Using Libvirt =