On Sunday 19 February 2006 05:06, Mike McCormack wrote:
> Mike Frysinger wrote:
> >>and adding a way to hide problems that probably don't belong to Wine in
> >> the first place.
> >
> > i dont understand what you mean here at all ...
>
> Perhaps give me an example of what doesn't work when you conf
On Saturday 18 February 2006 22:27, Mike McCormack wrote:
> It's good for people to build Wine without switching off features so
> that as much of the build as possible is tested on each machine.
so we're clear, it sounds like you wouldnt accept any patch for this
regardless of how it was written
On Sunday 19 February 2006 04:48, Mike McCormack wrote:
> Mike Frysinger wrote:
> > imo, the guy building the package knows more about the target features
> > than anyone else, and they should have the power to control what is and
> > isnt enabled ... forcing everyone to build everything they can a
On Saturday 18 February 2006 08:46, Mike McCormack wrote:
> Mike Frysinger wrote:
> > this patch adds a bunch of --without-FOO options to configure ... some
> > are very simple (like the sane/xml checks) while some others are slightly
> > more involved
>
> What's the point of crippling Wine like th
Mike Frysinger wrote:
this may be ok for most users who download and build themselves, but this isnt
useful for distro package maintainers
So, what is it that doesn't work in your packages when you configure
Wine the normal way?
Mike
Mike Frysinger wrote:
and adding a way to hide problems that probably don't belong to Wine in the
first place.
i dont understand what you mean here at all ...
Perhaps give me an example of what doesn't work when you configure Wine
the normal way, then we can talk about the solution to spe
Mike Frysinger wrote:
so we're clear, it sounds like you wouldnt accept any patch for this
regardless of how it was written ?
I'm not the one who accepts or rejects patches, so it's not me you have
to convince. I'm just reviewing your patch.
imo, the guy building the package knows more ab
Mike Frysinger wrote:
the point of the patch is to allow people to have finer control over the
featureset of wine ... for example, you wish to build on one machine but
deploy on others, you cannot be sure what features wine will require if the
build env has many more packages than the target
Mike Frysinger wrote:
this patch adds a bunch of --without-FOO options to configure ... some are
very simple (like the sane/xml checks) while some others are slightly more
involved
What's the point of crippling Wine like this?
Mike
