RPM

Still mark SRPMS with RPMTAG_SOURCEPACKAGE

Registered by Jeff Johnson on 2010-09-06

     Change: backward-compat-rpmtag-sourcepackage
     Purpose: Still mark SRPMS with RPMTAG_SOURCEPACKAGE
     Reason: For backward compatibility with RPM < 4.4.6 for all the
                     Fedora releases which are using RPM 4. RPM 5 will still
                     mark SRPMS with the RPMTAG_SOURCEPACKAGE. This especially
                     allows to switch between RPM 4 and 5 on Fedora. Without
                     this the mixture would involve manual "rpm2cpio" plus the
                     "rpm -bb" operation.

Blueprint information

Status:: Complete

Approver:: Jeff Johnson

Priority:: Medium

Drafter:: None

Direction:: Needs approval

Assignee:: None

Definition:: Obsolete

Series goal:: Accepted for 5.4

Implementation:: Needs Code Review

Milestone target:: None

Started by: Jeff Johnson on 2012-01-13

Completed by: Jeff Johnson on 2012-01-13

Related branches

Related bugs

Sprints

Whiteboard

This too is an ancient issue, phased out when rpm-5.0 was released.

The lack of a RPMTAG_SOURCEPACKAGE tag is a clear indication
of *.src.rpm for all SRPM's ever produced with no legacy consequences.

The only flaw is/was introducing an explicit tag into content; there already
is a header tag extension that is now common in the supported API to
retrieve tags from headers for legacy software that still tries to access
the tag now removed. The only remaining compatibility issue is
(and was in rpm-5.0 released 4 years ago) is when a package produced
by @rpm5.org is read by @rpm.org (or increasingly ancient releases of rpm).

There's no reason to carry this "legacy compatibility" retrofit into the future.

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information

Everyone can see this information.

Subscribers

No subscribers.

RPM