[pkg-wine-party] Moving forward after 1.2.3-0.1: proposed patches

[Michael Gilbert]

On Sat, May 12, 2012 at 6:54 AM, Hilko Bengen wrote:
> Hi,
>
> now that wine 1.2.3-0.1 has hit unstable, I'd like to propose a few
> patches. In the spirit of team maintenance, I'd like to get some
> feedback before I push those patches and work towards a 1.2.3-0.2
> upload.
>
> These patches do not introduce significant changes to the resulting
> binary packages: The list of build-dependencies has accumulated a lot
> of cruft in the last few years that is not necessary any more. It
> should no longer be necessary to depend on gcc-4.4 to build the
> package.

So, I think issues with a bug report are fair game for an NMU, but
otherwise, we should try to avoid things that are really cosmetic
clean ups (no matter how nice that would be).

My comments per patch:

1/8 and 2/8 - I already fixed this (differently) for the 1.4 series.
Do you disagree with my approach?
3/8 - This has an important bug report, so it would be good to fix it.
4/8 - Fixes an important bug, so its good.
5/8 - This is a cosmetic fix, so I think we should let the maintainer
handle this.
6/8 - Fixes an important bug, so its good.
7/8 - Fixes an RC issue, so its good.
8/8 - Includes some missing upstream files, so thats good.

wine 1.2 has some major issues on kfreebsd, so since it will take a
lot of work to get that in order, I think it would be better to put
all of our focus on making 1.4 solid for release at this point, rather
than putting any more effort into 1.2

> Also: Are there any objections to switching to source format 3.0
> (quilt)?

Yes.  We cannot do that because it would be a violation of NMU
procedures (even though I agree that it would be nice).

Best wishes,
Mike