RFE: record source NEVR

[hdonnay]

Currently, the only tags in an rpm relating to the source rpm seem to be

• SOURCEPACKAGE
• SOURCEPKGID
• SOURCERPM

Of these, only SOURCERPM seems to be populated consistently, and it contains a filename.
By convention this is a NVRA, which means that even when the convention is followed, there's no way to determine the epoch of a source rpm.

A new tag (SOURCENEVR) should record the source rpm's NEVR.

[pmatilai]

There's a ticket for tracking this case already: #2796

The thing is, some will want just the name, and some will want something else, and some will want the architecture too. So the question is, where does it stop?

[hdonnay]

The architecture will always be src, and the name can be extracted from a well-formed NEVR, so it should satisfy everyone's needs.

[pmatilai]

No, source architecture is not src. It reflects the architecture on which the src.rpm was built, which actually matters.

[hdonnay]

That sounds like "build arch."

Does an rpm's architecture (in the NEVRA context) not mean "target architecture"? It would be very surprising if it meant "architecture used for the build" when referring to a source rpm.

[pmatilai]

Actually, in this context the src architecture is actually irrelevant and can be considered "src" because the info comes from a binary to begin with. It's just that I've been repeating "source rpm architecture depends on the host used to generate the src.rpm" for so many years to so many shocked people that at the end of a long day, getting it mixed 😄

[hdonnay]

Okay, yes, I think that makes sense.
As in, if there were a SOURCE_ARCH tag, it would look like:

	pkg-1-1.src.rpm	pkg-1-1.noarch.rpm
ARCH	created arch	noarch
SOURCE_ARCH	(none)	src

[pmatilai]

(also see #1364)

[hdonnay]

done with #3755