> On Mar 4, 2017, at 5:43 PM, Jan Rękorajski <[email protected]> wrote: > > On Thu, 02 Mar 2017, Jeffrey Johnson wrote: > >> Here is the RHBZ bug report >> https://bugzilla.redhat.com/show_bug.cgi?id=1427287 >> >> This issue has been discussed ad nauseum back in 2009. >> >> PLD has 2 choices: >> >> 1) Retrofit RPMTAG_SOURCEPACKAGE and rpmlead boolean >> into RPM5 and rebuild everything >> >> OR >> >> 2) patch rpm.org rpm-4.13 (and perhaps older) with a couple line patch >> to recognize an RPM5 *.src.rpm (which rpm.org flatly refuses to do >> pmatilai <member:pmatilai>: rpm 5 interoperability is not a goal, at >> all:rpm 5 interoperability is not a goal, at all > > No it's not PLD choice. It's yours. > You are rpm maintainer and it's your concern if you want rpm5 be > compatible with rpm.org <http://rpm.org/>. >
The message was basically FYI. The code that needs changing is in rpm-4.13 (and the problem is worse than compatibility with RPM5: there are other applications that are producing headers without RPMTAG_SOURCEPACKAGE), so I will wait to see what rpm.org chooses to do (if anything). There’s lots of ways to detect a SRPM (e.g. file paths are relative, not absolute). This whole issue was hashed out in 2009 — little has changed since. 73 de Jeff _______________________________________________ pld-devel-en mailing list [email protected] http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
