12.07.2015 Views

Red Hat Enterprise Linux 5 Administration Unleashed

Red Hat Enterprise Linux 5 Administration Unleashed

Red Hat Enterprise Linux 5 Administration Unleashed

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Building RPM Packages139LISTING 5.9Continued%files%defattr(-,root,root,-)/usr/local/bin/%{name}%changelog* Thu Apr 27 2006 Tammy Fox - updated routes* Wed Feb 22 2006 Tammy Fox - first build of VPN scriptThe following describes the fields and sections from the spec file in Listing 5.9:NamePackage name. The name can not contain spaces.SummaryShort phrase describing the purpose of the package.5VersionSoftware version of the package.ReleaseLicenseGroupURLSource0Build number. Every time the package is rebuilt with the same version number,this number should be incremented so that it is clear a rebuild has occurred evenif the code has not changed. If a new version is built, this number goes back to 1because the version number indicates a code change and a rebuild.License for the software such as GPL, LGPL, or FDL for documentation.The software group for the package. It must be a valid group from the/usr/share/doc/rpm-/GROUPS file.Website location for the software, if one exists.Name of the file that contains the source and other files to be installed. The fileis usually a tar file compressed with either gzip or bzip2. Always use macros inthe filename such as %{name} and %{version} when possible. Doing so will resultin minimal changes to the spec file when other parameters change. If multiplesource tarballs exist, list them on separate lines and increment the number foreach file such as Source0, Source1, Source2, and so on.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!