I know that RedHat must get sufficient flack about the problems associated with rpms; however, I feel I must put my 2 cents in as well. This is the worst aspect of the OS. This is what really hinders RHL from taking over the world. I am a very patient person when it comes to PC's, which is why I work in this field. My customers can't understand how I am so patient when I am troubleshooting things. Yet I lose my patients trying to deal with dependencies. You need to add an app that needs 4 dependencies. You get out there on the net and find all four dependencies and download them to find the first rpm dependency requires 2 more, the second requires 4, the third thank god didn't need any and the fourth requires 2 more! Now we have 12 packages in addition to the original. That's not tough enough, now as we are installing one of them we have the problem listed below that one of the older versions is required for some other app to work so it won't allow you to install the new one. I know this has been described in detail and I really do love working with the OS in so many other ways so I'm not posting this to put down RH. It is just that for one, it is therapeutic to get this out. For two I also think there should be reminders from time to time that another operating system out there is configured in a manner that new software can be added without dealing with this kind of stuff. I think that the guru's of the world of whom I am unfortunately not a member of, should keep looking for a solution for the rest of us lower level shmucks.
Larry S. Brown Dimension Networks, Inc. (727) 723-8388 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, January 14, 2003 12:01 AM To: [EMAIL PROTECTED] Subject: RE: RPM dependency hell j_post <mailto:[EMAIL PROTECTED]> wrote on Tuesday, 14 January 2003 14:46: > I'm getting really tired of Red Hat's RPM nonsense. I can't upgrade > *anything* because rpm complains about dependencies. I can understand > that a new version of program 'xyz' may need library > 'libabc-2.3.so', but rpm > refuses to upgrade because program 'abc-1.2' depends on > 'libabc-1.2.so' and can't seem to deal with 'libabc-2.3.so'. Why > not??? > A major revision of a libray might involve revisions to the API (such as changes to function parameters, or contents of data structures) and so anything built with libabc-1 might crash with libabc-2. You often need to install both. Cameron. -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
