https://bugzilla.redhat.com/show_bug.cgi?id=1467322 --- Comment #10 from Adam Miller <admiller@xxxxxxxxxx> --- (In reply to Zbigniew Jędrzejewski-Szmek from comment #9) > I wouldn't sweat it. In decreasing order of compliance with the guidelines: > - just use a date: Provides: bundled(golang(golang.org/x/net)) = 20170305 > (where the date is the date where the vendorization was done or something) > - just use unversioned provides: Provides: bundled(golang(golang.org/x/net)) > > (The latter is pretty common, try "rpm -q -a --provides|grep bundled"... The > guidelines are well-intentioned, but if it's so hard to find which version > exactly is bundled, *and* this is something you'd have to do after every > update, I just don't think it's worth your time.) Neither of those options is in line with the Guidelines that went through FPC and FESCo for approval, please don't advocate for their use. Neither of those options provide a proper mechanism for auditing. I have opened a ticket with FESCo to determine appropriate action for dealing with all the not versioned bundled entries currently in existence. https://pagure.io/fesco/issue/1734 -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx
