On Sat, Jun 17, 2006 at 04:05:47PM +0100, Peter Tribble wrote: > ... > While blastwave does it, I can't use blastwave as a part of some > other solution. And that's the problem with all the package > management systems - they're fine, as long as you use them in > complete isolation. > > The underlying problem is dependency hell. And Ubuntu/Blastwave/ > whoever don't solve the problem - they hide it from the user and > therefore don't encourage the community to solve the basic problem.
You just contradicted yourself. The only way to guarantee a fix from dependancy hell (and have all the dependancies WORK, when you type [mumblety-upgrade]) is to ensure it all comes from the same place. I dont see any call for "the community to solve" this. it's a fact of life, living with free software. it's not a solvable problem. [unless you've come up with some miracle strategy to force free software authors to actually stick to sane release numbers, library naming, and binary compatible APIs unto themselves. ie: "berkeleydb". DISGUSTING! Now, how do you suggest the community "fix" that issue? ] It's certainly not a USER-solvable problem. They want it to "just work", usually. > As such, they only guarantee compatibility, consistency, and > stability amongst in their own self-contained universe. On home > machines that's probably enough, but it's certainly not good > enough once you need to do something the repository can't. There are multiple options, at least with blastwave, if it's software we dont already have: a) request someone at blastwave add the software you need (not guaranteed someone will pick it up) b) compile it locally against blastwave packages. yes, amazing, but this does actually work ;-) c) join up and volunteer to package it. Then you're pretty sure it will be as up to date as you need ;-) And if existing software doesnt have a feature you need.. File a feature request as a bug! _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
