Written by slashdotaccount the 14 Jun 10 at 13:39.

PROPOSED SOLUTION:
1. One program, one folder. All required libraries on one package. All dependent libraries of that program included in subfolders.
2. One exception: One system folder for "Shared Libraries". When installing a library, give an option to include it in that folder. System libraries like libc go to that folder. The package manager looks if a compatible library is in "shared library" folder to see if it can skip redundant copies.

PROS: Easy installation & uninstallation, removes dependency problems, removes compatibility problems, less orphan files, easy to implement, repositories easier to manage, installers much easier to develop, more compatibility with packages from other distros, fewer questions asked in forums, updates don't break unrelated software, closing the gates of hell.

CONS: Takes a bit more space in disk, might require a bit more memory if shared libraries aren't in shared library folder. Programs work on the non-shared libraries they were designed for, and not the updated ones (unless the developer updates the package himself). Developers must have faith in that there's something better than linux's dependency system of the 60-70s.

PROPOSED SOLUTION: 1. One program, one folder. All required libraries on one package. All dependent libraries of that program included in subfolders. 2. One exception: One system folder for "Shared Libraries". When installing a library, give an option to include it in that folder. System libraries like libc go to that folder. The package manager looks if a compatible library is in "shared library" folder to see if it can skip redundant copies. PROS: Easy installation & uninstallation, removes dependency problems, removes compatibility problems, less orphan files, easy to implement, repositories easier to manage, installers much easier to develop, more compatibility with packages from other distros, fewer questions asked in forums, updates don't break unrelated software, closing the gates of hell. CONS: Takes a bit more space in disk, might require a bit more memory if shared libraries aren't in shared library folder. Programs work on the non-shared libraries they were designed for, and not the updated ones (unless the developer updates the package himself). Developers must have faith in that there's something better than linux's dependency system of the 60-70s.

Written by drdanielfc the 30 Jun 10 at 13:50.

A program should be able to say "i want lib-watever v2.3." If the program fails to execute properly using the latest version of the library, then ubuntu should ask you to install the library version the program requested from the start

A program should be able to say "i want lib-watever v2.3." If the program fails to execute properly using the latest version of the library, then ubuntu should ask you to install the library version the program requested from the start