On Thu, 8 Oct 2009, Jesse Keating wrote:
On Thu, 2009-10-08 at 11:29 +0300, Panu Matilainen wrote:With that, the %{name} part is expanded at build time to effectively the source rpm name, and the rest is up to query-time expansion. The extension could return empty if the macro expansion fails (ie when _bugurl_os isn't defined). Something like fedora-release could provide the %_bugurl_os definition by default, and downstream distros, IT admins etc could override it to whatever appropriate. It also permits controlling the bugurl for packages from different sources like 3rd party repositories. And changing the bug tracker base address doesn't require mass-rebuild. That's trivial to implement, but would that be sufficient to cover the concerns over arbitrary downstream distros pointing to Fedora bugtracker etc, or should I just let it be?Hrm, how does it help for 3rd party packages? They would hardcode the entire string into their rpms?
They could hardcode the entire string or use their own macro for it, like %{_bugurl_myrepo} and provide a macro in their -release package that provides the macro definition.
- Panu - -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
