1,885
edits
Changes
→Release Dates, Presentations, and Quizzes
Previous semester: [[Fall 2010 SBR600 Weekly Schedule]]
** [[SBR600 Communication Tools|Communication Tools]]
** [[SBR600|Course Outline]]
* Overview of DeliverablesHow this Course Works
** [[SBR600 Communication Tools]]
** How coursework is submitted in SBR600
=== RPM Packages ===
* Purpose* What's in an RPM package fileDifferences between managing RPMS and Installing from Source** MetadataRPMS provide a database of installed software*** What the package providesLet you determine what's installed*** DependenciesAutomatic management of dependencies*** Packager, date, license, summary, description, ...** Digital signature** Software** Data*** Fonts*** Icons*** Sample data** Documentation** Configuration Identify the origin of files** Setup scripts*** Pre-installPermit easy update or removal*** Post-installEnable you to verify installation (useful for spotting file corruption and intrusions)*** Pre-uninstall*** Post-uninstall*** Triggers[[RPM Package Contents|Contents of an RPM Package]]
=== The RPM Database ===
* [[RPM Queries|Querying the RPM database]]
=== Layout of a specfile ===
* Basic Sections# preamble - basic metadata# %prep - commands to prepare the package for building# %build - commands to build the package# %install - commands to install the built files# %check - commands to check/test the built files (optional, often not included)# %clean - commands to clean up the disk space# %files - list [[Contents of files to be included in the pacakge# %changelog - record of the package's change-history* Scriptlets** %pre -- run before installation** %post -- run after installation** %preun -- run before uninstallation** %postun -- run after uninstallation*** Note that during upgrade, the installation of the new package is considered to happen before the removal of the old package.* Macros** %{_tmppath}** %{buildroot}** %{_bindir}** %{_datadir}** %{_mandir}** %{_smp_flags}** %setup** %configure** %makeinstallan RPM spec file]]
=== rpmlint: Checking for a clean spec file, SRPM, and RPM Creating Packages === <code>rpmlint</code> is a spec file, SRPM (.src.rpm), and RPM (.rpm) checker. To use it, supply the names of the file(s) to be checked as argument(s): rpmlint ''foo.spec foo*.rpm''
=== Demo: Creating a Simple Package ===
* Writing the specfile
* Testing the specfile
** Using rpmlint
=== Resources ===
== Tuesday ==
=== mock: Testing BuildRequires Project Selection === This is a project-based course. These projects involve participation in an open-source community.* Projects are listed on the [[SBR600 Potential Projects]] page.* Select two or three projects that are of interest to you.** Do some initial research into what the project involves.*** Find out who to talk to in the community (start with the initial contacts listed on the project description)*** See what work has already been done related to that project. Check the Seneca wiki for work by previous SBR600 semesters, the upstream project's wiki and mailing list archives for information about the current state of the project, and the web for related information (similar projects being done by other groups).*** Join the mailing lists and IRC channels of the upstream community.** Update the [[Winter 2011 SBR600 Participants]] table with your project information, according to the instructions at the top of that page.* [[User:Chris Tyler|Your professor]] will approve your project selection via the [[Winter 2011 SBR600 Participants||participants page]].* Link your project title on the [[Winter 2011 SBR600 Participants|participants page]] to a page of the same name to create a project page. Copy the contents of the [[Sample Project]] page to your project page and fill in the details.
=== 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.
* mock
** [[:fedora:Projects/Mock|Mock Project page]]
** [[:fedora:PackageMaintainers/UsingKoji|Using Koji]]
=== ToDo === * [[SBR600 Mock and Koji Lab|Mock and Koji Lab]] = Week 3 (January 24) - Solving Build Issues = = Week 4 (January 31) - Project Plan Presentations = == Tuesday ==
= Week 4 5 (January 31February 7) - Repositories/Distributing =
== Signing RPM packages ==
# Create a GPG key: <code>gpg --gen-key</code>
# Add the e-mail address associated with your gpg key to the <code>%_gpg_name</code> macro in <code>~/.rpmmacros</code> -- the line will look like this: <code>%_gpg_name "<i>e-mail-address</i>"</code>
# Find (or make) some packages to put in your repository. Make sure that the epoch-version-release is higher than that of any package with the same name in the Fedora repositories.
# Sign those packages with: <code>rpm --addsign <i>packagefile</i></code>
== ToDo ==
Lab
# Test it.
# Blog about this lab, and include a link to your repository RPM package.
= Weeks 6 - 13 =
* Project work
= Release Dates, Presentations, and Quizzes =
* March 7 - '''Release 0.1'''
* March 15/17 - Pre-0.2 presentations
* March 24 - Written Quiz
* April 4 - '''Release 0.2'''
* April 5/7 - Pre-0.3 presentations
* April 11/13 (To Be Confirmed) - OCE Presentations
* April 14 - Practical Quiz
* April 22 - '''Release 0.3''' - DO NOT BE LATE!
<!-- = Week 8 =