> Yes. I have the same question. Using apt, I can update redhat system > packages easily. However, when I install non-redhat packages, apt is not > useful at all. > > Bo
Yep, found that out yesterday too when I got apt installed and running. It's lightyears away from being a perfect solution as well. Bugger. What is the tricky part about all this though? A lot of dependencies I come across simply say something like 'libsoandso.x.y.x.so >= 3.22' needed. Great. Wonderful. Which RPM then has that libsoandso? Apparently rpmfind.net lets you search on not just RPM names but what requires, provides, whatever. But whenever I get one of these lib dependencies, typing it into the search box gives me nada. Life would be so much easier if instead of specifying individual files, RPM simply tells you 'get RPM(x) to satisfy dependencies'. Now, I realise RPM wouldn't have a clue which files contain what, but can't the builder of the RPM provide that information when building the package? Add to that different RPMs from different distributions need different file locations/dependencies as well. Linux has been around for quite a while now, but we're still battling this. As far as the different distribution RPMs go, at least that will significantly lessen when we only have the two: UnitedLinux and RedHat. But really the way we install things sux the big one. Can we get InstallShield for Linux? Regards, Ed. -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
