[pkg-wine-party] Bug#819255: nothing depends on wine-binfmt
jre.winesim at gmail.com
Tue Jan 30 19:29:32 UTC 2018
control: tags -1 pending
On 01/19/2018 08:41 PM, Adam Borowski wrote:
>> This has also been brought up upstream in #39884 for their packages, and
>> is now being discussed in wine-devel
> The discussion ended without a conclussion, be it for yes or for no.
> Upstream's packages are monolithic, though, without a separate binfmt
> package, thus it's a valid dilemma there. Your packaging is different.
>> We might also add a low priority debconf question (default false) to
>> setup the binfmt support.
> I just realized: as there's nothing that can make wine-binfmt automatically
> installed (the only relationships are Suggests:), this question has already
> been answered by the user: they made the manual step of installing this
> package. On Debian, it is split out, and has no other contents than the
> Thus, every user who would want to answer "no" to such a debconf question
> wouldn't install the package.
I reread #733556 (binfmt-support got lost for PE32+) and follow-up bugs,
which already have some discussion of this topic. They discuss the
security risks, and the risk of running an application already installed
in another prefix in the wrong prefix. The 64-/32-bit issues mentioned
in these bugs are solved by the current Wine setup. It seems nobody
explicitly objected activating binfmt-support as long as it is in a
So I agree with Adam, and therefore committed the needed postinst and
prerm scripts to git (also attached to this mail).
I will not make an upload with these changes for at least 2 weeks, to
give everyone a chance to raise their voice.
I also updated the package description and the README, and added a NEWS
entry. Please have a look at them, and tell me what you think.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 6752 bytes
Desc: not available
More information about the pkg-wine-party