The Monday 2004-12-13 at 01:49 +0100, Joerg Mayer wrote:
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?
No. If _I_ order a package to be tabooed, for my own reasons, I want it to keep tabooed the next time I open Yast. I do not want Yast to choose to forget my settings. At most, Yast should ask if I'm still sure I want to keep my taboo. I'm root. I order, yast obeys. IMNSHO. At present, I have to keep my list of tabooed packages on a sticker, and re-taboo them every time I use yast to install or remove a package. If I get tired of this, I create my own empty rpm to fool it.
I don't see why wine should require it.
Have you ever considered to investigate this?
¡Yes! So I ask if somebody knows, who can investigate it better than me, or who already knows. Do you object to that? That's the reason of mail list such as this, sharing knowledge, - and if you investigate me, you will find dozens of my answers per a single question.
<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".
_I_ haven't critizised SuSE. That was somebody else. Look again.
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.
I thought of something on that line. Thanks for the explanation. -- Cheers, Carlos Robinson