re to understand
what Jeremy is saying. Apple has very strict non-disclosure policies
with respect to unreleased products. What Jeremy is saying here is
that Wine has a compile conflict with an upcoming Apple product
(probably a version of Xcode, but possibly a version of MacOS), but he
can't
e the ones that don't work, which seem to me to be the ones
that need effort.
--
Mark Wagner
age non-Wine user of this software has only a vague idea of
what's going on inside the box on their desk. Asking the user what
disks should be scanned will get blank stares and wrong answers 99% of
the time.
--
Mark Wagner
On Mon, Sep 29, 2008 at 14:55, Juan Lang <[EMAIL PROTECTED]> wrote:
>> Did you read the second paragraph of my original email? I'm not
>> working around a bug in Wine, unless it's a bug that a user can map
>> "/" to "C:" and call it a "fixed disk".
>
> Yes, I read it. And scanning "/" shouldn't b
g around a bug in Wine, unless it's a bug that a user can map
"/" to "C:" and call it a "fixed disk".
--
Mark Wagner
as
there's not a one-to-one mapping between disks and drive letters, and
there's usually at least one way to access the entire *nix filesystem.
If someone's got a few network drives mounted, the installer could
spend hours searching them.
--
Mark Wagner
