[Bug 225778] Merge Review: gcc

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Merge Review: gcc


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=225778





------- Additional Comments From toshio at tiki-lounge.com  2007-02-08 13:02 EST -------
We've had some initial conversations on #fedora-packaging which is leading to
these thoughts:

1) The original reason for the guideline was to prevent foo-1.0.tar.gz => bar.spec.
2) Preserving history is a perfectly valid wish.
3) comparing two versions of the spec could be done with the SCM's diff command:
   cvs diff -u -r qa-assistant-0_4_1-4_fc5 -r HEAD qa-assistant.spec
   for instance.

So my current thought on a proposal is:
'''
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 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 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 *lose* history:
  * gcc
  * [Please ask the packaging committee to add your package if you think it
should fall under this exception as well.]

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 imported into cvs.  When gcc is upgraded to gcc-4.2, the new spec will be
created as gcc.spec)
'''

This text will appear on:
  http://www.fedoraproject.org/wiki/Packaging/NamingGuidelines
and be linked from:
  http://www.fedoraproject.org/wiki/Packaging/ReviewGuidelines

Let me know if this addresses your concerns or if you have some ideas to make it
better.  I'll post it to fedora-packaging later today if you have no objections.

-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.