loader manpages get installed in wrong build step
marcus at jet.franken.de
Mon Nov 2 02:18:08 CST 2015
On Mon, Nov 02, 2015 at 10:33:30AM +0900, 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
> > 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?
Main issue is that the x86_64 package does not install the "wine" manpages, as the
binary is called wine64.
Not a big issues, it can be worked around.
More information about the wine-devel