https://bugzilla.redhat.com/show_bug.cgi?id=1366411 Jason Tibbitts <tibbs@xxxxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(tibbs@xxxxxxxxxxx | |) | --- Comment #9 from Jason Tibbitts <tibbs@xxxxxxxxxxx> --- I'm sorry, what's not transparent? This is just a package. There's not currently anything actually in it. It's gone through the proper review procedure. It's intended for future use, so we don't keep having to mess with redhat-rpm-config, which is rather more complicated than it needs to be for something that drops in some macro files. Plus it has a rather odd versioning mechanism. This gives me one package I can untag if necessary, without worrying about conflicting with other macro maintenance done by the RPM maintainers. And without using provenpackager privs to get FPC-approved macro work done. Having a package which can hold things like the GPG macros which the packaging committee has been discussing (and which will begin going in as soon as I can find the time) is beneficial. That's the original reason this package was created. I can see no downsides of that. Also note that plenty of other macro packages are now required by redhat-rpm-config. I don't see this trend going away. I also don't see what relevance RHEL/Centos has to this discussion. If EPEL needs these macros for compatibility, they'll go into epel-rpm-macros. If Red Hat wants to follow whatever obviously completely transparent process it has for doing whatever it wants to do internally, then it will and Fedora/EPEL will end up adapting as they always do. That would be no different regardless of where the actual macros are stored. Thanks for the tip about install. It's always bugged me that it doesn't just work like you'd expect by default. -- 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