Hi all,
The new spec file naming guideline was passed last week and became
official today. It's basically a clarification of why the current
guideline exists and includes a clause for allowing Core packages to be
accepted with an alternate name under certain conditions.
If you maintain a Core package that you want included in the exception,
please send a note to me or the packaging committee so we can add your
package to the clause.
-Toshio
Text of new guideline below::
== Spec file name ==
The spec file should be named using the %{name}.spec scheme. This is to
make it easier for people to find the appropriate spec when they install
a src.rpm.
Example:
{{{
If your package is named foo-1.0.0-1.src.rpm, then the spec file should
be named foo.spec.
}}}
There is normally no need to include the `%{version}` in the spec file
name. If you are packaging multiple versions of a package for
simultaneous use, they should already reflect the version in the `
%{name}.spec` scheme (refer to [#MultiplePackages Multiple Packages with
the same base name] for details). In normal cases adding the version
can cause the spec file's history to be lost when a package's version is
upgraded.
As a special exception, there are a few packages which are allowed to
have a version in their spec filename. This is because they had the
version in their name when they were merged from Fedora Core's cvs and
removing the version at that time would have *lost* history:
* gcc
* [Please ask the packaging committee to add your package if you think
it should also fall under this exception.]
This exception will go away when any of the following criteria are met:
1. We move the packages to a revision control system which is able to
preserve history across a file rename.
2. The package spec file is going to be renamed anyway (for example,
gcc41.spec is currently in cvs. When gcc is upgraded to gcc-4.2, the
new spec will be created as gcc.spec '''not''' gcc42.spec)
Attachment:
signature.asc
Description: This is a digitally signed message part
-- Fedora-maintainers mailing list Fedora-maintainers@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers
-- Fedora-maintainers-readonly mailing list Fedora-maintainers-readonly@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers-readonly
