To view parent comment, click here.
To read all comments associated with this story, please click here.
This PC-BSD packaging thing is just a mistake.
Is it a mistake for you because of philosophical reasons or because of technical reasons? If it's for technical reasons, this has been discussed a number of times, and there is nothing wrong having several times the same libraries on your system. It just uses a little bit more RAM/HDD, which is a tradeoff they decided to choose, update allows you to have a secure system, and they did the right choice because their PBI system works remarkably good.
What better solution do you suggest instead of their technique, keeping installation like the PBI concept using a self-extracting package for the end user and to solve the dependency nightware of other systems? (DesktopBSD's package system is no-go for Windows and Mac users).
"""Is it a mistake for you because of philosophical reasons or because of technical reasons?"""
Technical, of course. Is there some deep philosophical dimension to all of this that I am missing?
A large, complex OS without shared objects is like a large complex program without functions (or methods or the equilvalent). Sure, you can do it. But it'll be a mess to maintain, and it won't be very efficient.
At any rate, it's no skin off my nose. I've decided to just sit back and wait, and watch as the "no dependencies" crowd figures it out for themselves.
Edited 2006-10-31 14:16




Member since:
2005-07-24
"""You say that because you're jealous. They were the first to put this into practice and implement the same installation procedure as Windows applications."""
No. I say it because it is true. I do happen to prefer Linux. But I feel that Linux and BSD are brothers and applaud the BSDs when they do cool things like reverse engineer wireless drivers. They are beating our butts on that count.
This PC-BSD packaging thing is just a mistake.