Linked by Stefan Michalowski, M. Sc. on Thu 19th Aug 2004 08:27 UTC
Permalink for comment
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/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



> Yes, I know, there are packages and package-handling
>software, but quite too often, those fall just short of
>doing "the thing" for you. More often than not, I had to
>take manual action - because the ebuild for Subversion
>wasn't yet up to 1.0, because the RedHat db4 RPM was
>compiled with an option that hickuped on my server...
Let me ask you this, what would you do with closed-source software if you had the same problems? You would have to contact all those companies and ask them to fix the problems and then wait. With Free software, you fixed all this yourself.
I agree that fixing is not easy and free, it does require time and money, but it's better spending that time and money on fixing the real issue instead of creating workarounds that create wholes in other software (A has a problem and I fix B to make it work with A but at the same time I create a whole in B).