[Guidelines Change] Changes to the Packaging Guidelines

Here are the latest changes to the Fedora Packaging Guidelines:
---
Some rpm versions pass pathnames to the automatic filtering macros, so a
section has been added to the guidelines to help packagers deal with it:
https://fedoraproject.org/wiki/Packaging:AutoProvidesAndRequiresFiltering#Pathnames
---
For a while, Fedora considered mono packages to be
architecture-specific, and installed assemblies to %{_libdir}. However,
after discussions with upstream, we now consider mono packages to be
architecture (and platform) independent. This means that mono packages
should be correctly installed into the GAC in /usr/lib or installed into
/usr/lib/PACKAGENAME.
As a notable exception, any ELF binary libraries generated in a mono
package must be correctly installed into %{_libdir}, because these files
are architecture-specific.
Also, even though we consider mono packages to be architecture
independent, they must not be marked as "noarch". Although the
assemblies are the same, the files may differ due to strings referring
to the build architecture.
https://fedoraproject.org/wiki/Packaging:Mono#File_Locations
---
It was decided that gnome shell extension packages should have the
prefix gnome-shell-extension (with no "s" on the end).
https://fedoraproject.org/wiki/Packaging:NamingGuidelines#Addon_Packages_.28gnome_shell_extensions.29
---
The section in the Fedora Packaging Guidelines concerning libexecdir has
been improved and expanded:
https://fedoraproject.org/wiki/Packaging:Guidelines#Libexecdir
---
The Fedora Java Packaging Guidelines have been updated to reflect the
latest macros for Maven 3.
https://fedoraproject.org/wiki/Packaging:Java
---
These guidelines (and changes) were approved by the Fedora Packaging
Committee (FPC).
Many thanks to Christian Krause, Aleksandar Kurtakov, Petr Pisar,
Stanislav Ochotnicky, and all of the members of the FPC, for assisting
in drafting, refining, and passing these guidelines.
As a reminder: The Fedora Packaging Guidelines are living documents! If
you find something missing, incorrect, or in need of revision, you can
suggest a draft change. The procedure for this is documented here:
https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure
Thanks,
~spot