| |||||||||||||
Conflicts?Conflicts?Posted Dec 2, 2003 19:15 UTC (Tue) by southey (subscriber, #9466)Parent article: New features in APT-RPM "Dependencies are automatically handled, so if one tries to install a package that requires others to be installed, it will download all needed packages and install them." So what happens to old versions that are required by other programs? Especially older and poorly maintained projects require old libraries so you end with conflicts that are not easy to resolve. Even things like the new threads in the kernel meant some projects (like Wine) crashed and these take time to get resolved.
(Log in to post comments)
Conflicts? Posted Dec 2, 2003 19:25 UTC (Tue) by TimCunningham (guest, #10316) [Link] Generally (at least in my experiance, with Debian) what happens is that the latest version of the library that breaks things will be held off until all of the other software is made to work with it. This means you sometimes get delays in having the latest everything.
Conflicts? Posted Dec 2, 2003 21:22 UTC (Tue) by JoeBuck (subscriber, #2330) [Link] In such cases (where some programs need an old version and some need a new version of some package), apt will tell you that if you proceed with the install, certain packages will be removed, and will then ask you if you want to proceed. Then it's up to you to choose.
Conflicts? Posted Dec 11, 2003 14:04 UTC (Thu) by Peter (guest, #1127) [Link] Especially older and poorly maintained projects require old libraries so you end with conflicts that are not easy to resolve. The usual solution to that problem is, when a new library comes out which is not ABI-compatible with an older version, the new one gets a new name. And installs itself so as not to stomp on the old version. At least that's how things are done with sane developers and distributors. If your version of Linux doesn't do that as a matter of course, you ought to consider upgrading to one that does.
|
|||||||||||||