Re: search path redux - if office 2007 always uses a private riched20, why does wine interpose its own global one?

[James Mckenzie]

Austin English <austinenglish(a)gmail.com> wrote:
> Sent: Feb 17, 2009 7:27 AM
> To: Alexandre Julliard <julliard(a)winehq.org>
> Cc: "wine-devel(a)winehq.org" <wine-devel(a)winehq.org>, Dan Kegel <dank(a)kegel.com>
> Subject: Re: search path redux - if office 2007 always uses a private 	riched20, why does wine interpose its own global one?
>
> On Tue, Feb 17, 2009 at 6:07 AM, Alexandre Julliard <julliard(a)winehq.org> wrote:
> > Dan Kegel <dank(a)kegel.com> writes:
> > > See http://bugs.winehq.org/show_bug.cgi?id=14980
> > >
> > > Essentially, to run Office 2007, you have to set an override
> > > for riched20.  Since Office installs a new, spiffier version
> > > of riched20 in its own private directory, and expects to
> > > find it there, isn't it a bug that we don't let it have it?
> >
> > There's no guarantee that using the private version would help. In some
> > cases it does, in other cases it makes things worse. So defaulting to
> > builtin is preferable, this way at least when it doesn't work we have a
> > chance of fixing it.
>
> What happened to 'bug for bug compatibility'?

Austin:
These are considered private dlls as they extend functions that do not exist in the original system dll.  When they are incorporated into the standard system dlls, then the new functions, and bugs, should be incorporated into the Wine versions.  I think this is what AJ and Dan K are saying.

James McKenzie