On Sun, Dec 12, 2004 at 10:56:00PM +0100, Carlos E. R. wrote:
It would make sense, as it is true that YOU can install a tabooed package without the user noticing. I don't understand why a "taboo" does not keep "tabooed".
Perhaps because you want'S to work in a consistent rpm environment where all dependencies are fulfilled?
I don't see why wine should require it.
Have you ever considered to investigate this?
<RANT>
What is really annoying about this thread is, that people are criticizing
Suse - in some cases in very bad wording - for something that is clearly
for the wine developers to fix, and not Suses "fault". Has anyone who
doesn't see this looked into the wine sources and perhaps grep'ped for
"isdn" (no relevant hits) or capi (relevant hits).
Just an important rule as far as security is concerned: THINK before you
ACT. In case you can't be bothered to do that, please assume that you are
incapable of getting anywhere as far as security is concerned.
</RANT>
Investigarion of the wine sources leads to the following: wine tries to
implement all the upper layer APIs that are present in a basic Win install.
Windows does have ISDN support, the API to the ISDN world is called CAPI.
Wine uses the linux capi stuff to implement the windows API. The Suse
wine package is being built with capi support and thus some isdn-stuff
needs to be installed for wine to be able to use it.
ciao
Joerg
--
Joerg Mayer