Linked by Thom Holwerda on Mon 30th Oct 2006 19:43 UTC, submitted by Charles A Landemaine
Permalink for comment 177124
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
2006-01-23
It is true there are some technical issues that need solving but the easy way for users is the right way.
The problem with shipping with full dependencies comes from open source software.
In closed source software rarely do companies use shared libraries as they are plagued by copyright and patent issues.
Open source on the other hand is all about sharing. This means most projects use shared libraries. Now this is not te actual problem. The problem is library writers keep breaking compatibility with older versions as new ones ship. Aditionally, there seems to be no teamwork from the library maintainers and app maintainers to do joint testing before libraries ship.
This means the shared library maintainer will work on the library to achieve whichever his goals are (for his app) and releases it even if it breaks other apps using it. This is bad.
I see some ways out of this.
1- Lib maintainers and lib users work together and libs take a little bit longer to release but keep backwards compatibility.
2- Libs start being named with full version number "libblabla2.2.3.4" so they can be used side by side with different versions and app maintainersupgrade when they are ready.
3- Something like GoboLinux
4- PBI
Dependencies are not an option, this issue must be killed.
Having said this, the PBIs are the best end user experience so far when well built. notice this is sometimes hard as some apps are just nasty either because legal reasons or technical.
But as i agree the PBIs aren't perfect YET, i think PC-BSD is on the right way...