loader manpages get installed in wrong build step

Sebastian Lackner sebastian at fds-team.de
Sun Nov 1 20:44:29 CST 2015

On 02.11.2015 02:33, Alexandre Julliard wrote:
> Sebastian Lackner <sebastian at fds-team.de> writes:
>> Hiho,
>> I've noticed another side effect introduced by
>> http://source.winehq.org/git/wine.git/commit/da340169d6518cf42f1cbe169fbf120383202bdc,
>> and I'm not sure if its intentional, or if its a bug.
> It's intentional, in the sense that the manpages should go along with
> the corresponding binary. So the wine manpage is installed when the wine
> binary is installed, which in a wow64 setup means on the 32-bit side
> (arguably we should also have a wine64 manpage installed on the 64-bit
> side).

I agree, it probably makes more sense than the previous solution.
Thanks for the clarification.

>> When both builds end in the same package (like on Archlinux) this doesn't matter,
>> however there are plenty of distributions which ship the 32-bit and 64-bit
>> parts in different packages. Having a few manpages in one and the rest in the
>> other is at least a bit unusual, but could also lead to package conflicts.
> I'm not sure I understand why it would be a problem to have the 32-bit
> package install manpages. What issues do you see?

Its not really a problem, but it requires changes in most distro packaging scripts.

Best regards,

More information about the wine-devel mailing list