= Week 3 (January 26) - Creating RPM Packages and Working with Open Source Communities = = Week 5 (Sept 29) - Creating SPEC files and RPMs = == RPM Packages == * Purpose* What's in an RPM package file** Metadata*** What the package provides*** Dependencies*** Packager, date, license, summary, description, ...** Digital signature** Software** Data*** Fonts*** Icons*** Sample data** Documentation** Configuration files** Setup scripts*** Pre-install*** Post-install*** Pre-uninstall*** Post-uninstall*** Triggers == The RPM Database == * Purpose of the database* Querying the RPM database** rpm -q == Creating Packages == * Packaging scenarios* Setting up a Packaging Environment** Needed packages*** rpm-build*** rpmdevtools*** rpmlint** Setting up the RPM tree*** run <code>rpmdev-setuptree</code>* Source RPMS** Installing ** Examining the contents** Rebuilding*** <code>rpmbuild --rebuild *.src.rpm</code>** Building from the spec file == Writing a specfile == * <code>rpmdev-newspec ''packagename''</code>* 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 of files to be included in the pacakge# %changelog - record of the package's change-history* Scriptlets** %pre** %post** %preun** %postun* Macros** %{_tmppath}** %{buildroot}** %{_bindir}** %{_datadir}** %{_mandir}** %{_smp_flags}** %setup** %configure** %makeinstall == Creating a Simple Package == * NLED* Writing the specfile* Testing the specfile* Using rpmlint == Resources == * [[:fedora:PackageMaintainers|Fedora Package Maintainers page]]** [[:fedora:PackageMaintainers/CreatingPackageHowTo|Packaging How-To]] See also "Fedora Linux" chapter 5 (see Seneca Library website > eBooks > View All > Safari > Fedora Linux). '''TODO:''' * Take the software you compiled last week and package it (not Nled!). Blog about the experience. Include a link to your source RPM (and optionally your binary RPM) from your blog.