No edit summary |
(→Exception to spec naming still valid?: new section) |
||
Line 16: | Line 16: | ||
Suggest change to: | Suggest change to: | ||
"followed by between 2 and 16 (ASCII) alphanumeric characters of your choosing." | "followed by between 2 and 16 (ASCII) alphanumeric characters of your choosing." | ||
== Exception to spec naming still valid? == | |||
Does the following still need to be included in this document? | |||
{{Quote| | |||
== Spec file name == | |||
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. 1. 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)|}} | |||
gcc is at gcc-4.6.0-9.fc15 currently, so I assume its spec has been renamed. Regardless, the packaging system is now using git, which I believe ''does'' preserve history across file renames, doesn't it? --[[User:Ferdnyc|Ferdnyc]] 12:55, 22 June 2011 (UTC) |
Revision as of 12:55, 22 June 2011
The following metadata was found in MoinMoin that could not be converted
to a useful value in MediaWiki:
- : Note that Epoch: has been dropped here, but preserved in Provides/Obsoletes below
Clarification request
" Snapshot packages
If a snapshot package is considered a "pre-release package", you should follow the guidelines listed in Pre-Release Packages , and use an %{alphatag} beginning with the date in YYYYMMDD format and followed by up to 16 (ASCII) alphanumeric characters of your choosing."
Is there a minimum number of alphatag chars ? Would 2 be a good minimum eg: fits hg
Suggest change to: "followed by between 2 and 16 (ASCII) alphanumeric characters of your choosing."
Exception to spec naming still valid?
Does the following still need to be included in this document?
|
gcc is at gcc-4.6.0-9.fc15 currently, so I assume its spec has been renamed. Regardless, the packaging system is now using git, which I believe does preserve history across file renames, doesn't it? --Ferdnyc 12:55, 22 June 2011 (UTC)