Parameterizing the places Wine suggests people report bugs

[Austin English]

On Mon, Mar 18, 2013 at 5:18 PM, Josh DuBois <duboisj at codeweavers.com> wrote:
> Hi all,
>
>   There are a couple of places wine suggests that people report bugs to
> wine-devel.  The crash reporting dialog in winedbg suggests this, and a
> couple of places in code refer to wine-devel at winehq.org in error messages.

I assume you meant http://bugs.winehq.org for the winedbg dialog,
since that's what I get/the po files refer to:
"Report-Msgid-Bugs-To: http://bugs.winehq.org\n"

>   The configure script has a PACKAGE_BUGREPORT macro which could be used to
> allow someone building wine to redirect those errors somewhere else.
>
>   At least for wine's crash dialog, an alternate approach for a repackager
> to redirect bug reports would be to read the url / email address for where
> to send bugs from the registry.
>
>   Would Wine accept a patch for making winedbg read the 'destination' for
> bug reports from the registry or some other runtime variable?  Or would the
> project prefer to have all the bug reports routed directly to winehq, so
> that a repackager who wants to re-route bugs would have to build that
> facility on its own?

I can't speak for Alexandre, of course, but speaking with my bugzilla
hat on, if a packager wants to override that, I don't see the harm.
I'd rather see wine bugs reported upstream (i.e.,
http://bugs.winehq.org), but if the packager wants to override that, I
assume they have a good reason (building wine with custom/hacky
patches, changing default registry settings, etc.).

How many packagers will actually use that feature though, and how many
users would notice the difference, is the ultimate question, of course
:).

-- 
-Austin