[pkg-wine-party] Bug#585409: Too ambitious!
ovek at arcticnet.no
Wed Mar 28 15:55:02 UTC 2012
On 03/28/2012 04:49 PM, Ivan Baldo wrote:
> Hello Ove!
> I appreciate your work and time, what follows is just a constructive
> opinion for your consideration.
> Many of the things you mention are really upstream bugs and considering
> your limited time it would be best just to delegate that work to
> upstream (coinstallability, multiarch, etc.).
Hardly. Such things are packaging issues, not upstream issues. In the
case of multiarch, anything they might possibly do would probably
actually be in direct conflict with the way things are supposed to work,
and thus just compound the packager's headaches, not alleviate them. For
most packages (including Wine), multiarchification involves
intentionally overriding upstream's build system defaults in ways only
the distribution-specific packaging system really needs to know.
Upstream's job is only to allow this kind of override, nothing more;
doing the actual override is the packager's job. Wine's upstream has
already done what they need to do.
> Instead of aiming for perfection and missing Wine 1.4 in Wheeze
Pff. What's left to do in that plan should probably take a skilled and
motivated volunteer about a week or so of work. Packaging Wine 1.4
afterwards, maybe another week. For various practical reasons (including
this not being anyone's day job), you'd probably have to multiply this
with some fairly significant number to get the real time it'll take, but
even then, it'd still leave a comfortable amount of time left until Wheezy.
As I said, the reason I haven't done it myself is because I've already
been backlogged up to my ears with everything else I'm supposed to be
doing. It's not because it would have been an enormous job.
More information about the pkg-wine-party