RPM

package naming rules still confusing/restrictive

Bug #1327904 reported by Jeff Johnson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
RPM
New
Undecided
Unassigned
lsb
In Progress
Medium
Unassigned
Mandriva
Won't Fix
Medium

Bug Description

This is a quote from packaging 0.2-20040406 as included in LSB-Core
1.9.6-20040407:

If the package name contains more than one hyphen (i.e.,
"lsb-www.redhat.com-redhat-database", "lsb-gnome-gnumeric"), then the
portion of the package name between first and second hyphens shall
either be an LSB provider name assigned by the LANANA, or it may be
one of the owners' fully-qualified domain name in lower case (e.g.,
"debian.org", "staroffice.sun.com"). The LSB provider name assigned
by LANANA shall only consist of the ASCII characters [a-z0-9].

However this eliminates the common usage of dividing a package into a main
package with optional subpackages suffixed with -<sub>. For example, if the
package name "rpm" were registered, then lsb-rpm is a legal name but
lsb-rpm-python (for the optional Python language bindings) is not by the "more
than one hyphen" rule.

Also, the same section should be clear if it's referring to the Name tag in the
package, or the package filename. The package filename is conventionally
constructed as <name>-<version>-<release>.architecture.rpm and thus would put
it
in the "more than one hyphen" category. The spec should clarify that there is
no requirement on the filename, but perhaps indicate the convention.

Tags: spec lsb rpm zpunt
Changed in mandriva:
importance: Unknown → Medium
status: Unknown → In Progress
Jeff Johnson (n3npq)
tags: added: rpm
tags: added: lsb
Jeff Johnson (n3npq)
tags: added: zpunt
Changed in mandriva:
status: In Progress → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.