https://bugzilla.redhat.com/show_bug.cgi?id=1428035 --- Comment #11 from Neal Gompa <ngompa13@xxxxxxxxx> --- (In reply to Petr Šabata from comment #8) > (In reply to Neal Gompa from comment #7) > > (In reply to Petr Šabata from comment #4) > > > (In reply to Neal Gompa from comment #2) > > > > This should be prefixed with fedora- in its name. This is *not* generic. > > > > > > Note this package is only meant for the module-based compose and it is the > > > only variant we're going to ship. Putting "fedora" in the name feels > > > redundant to me, even if its content in Fedora dist-git includes files > > > specific to Fedora. > > > > > > Also note this package won't be part of the traditional release -- it will > > > be excluded from the compose. > > > > The name in the Summary indicates it's Fedora specific. All fedora branding > > packages are named fedora-*. This should be no different. > > The idea here was that we wouldn't have to change the package name, > bootstrap tags and installation & buildroot profiles when [re]building > modules outside of Fedora. Of course this isn't the only way to achieve > that; we could rename it or package this differently, if you really insist > on having Fedora in the package name. I do, especially since this conflicts with the regular "fedora-release" and calls itself "Fedora modular release". I firmly believe it should be clear for Fedora branding so that downstream consumers of Fedora have a clear direction on what packages they need to replace, even when making their own "modular" distributions. Please rename this package. If you want to also produce a "generic" version for people to use as a template for downstream use (which would be greatly appreciated), that would be excellent too. -- 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