On Wed, 2006-03-29 at 14:30 -0500, Peter Jones wrote:
Ok, but there's a more serious problem there. If you're
moving the
package from core to extras or vice versa, start with the same spec file
and only change the parts you actually have to.
If our naming policy for extras says we have to use one particular
capitalization for a "release" field, then we should fix it. That's
just a rule for the sake of having more rules. It doesn't buy us
anything.
In extras, we use a %{dist} macro in the spec, that's automatically set
by the build system. And the build system uses lowercase. That's the
rule.
What does this rule buy us? The same spec can be used to build for
multiple distro versions.