> I would like to confirm as below: > > In sunfreeware.com, under x86/Solaris10, there is: > - > ftp://ftp.sunfreeware.com/pub/freeware/intel/10/ncurse > s-5.6-sol10-x86-local.gz > And in www.blastwave.org, there is also: > http://www.blastwave.org/packages.php/ncurses > ncurses 5.5,REV=2006.02.10 ncurses library and > utilities > > So which one is should be download over which one?
Other blastwave packages will most likely have dependencies on their version. That might be true for the sunfreeware.com stuff as well, although I haven't used any recently, so I don't know that for a fact. And there's probably one with the Companion CD stuff, too, which probably includes other packages that depend on their own ncurses package. Perhaps the question is only meaningful for unpackaged, built-it-yourself stuff, and then it would be a matter of making sure you had one of a suitable version for whatever you're building; you might well want to just build your own, so that if you had a mix of your own and prepackaged stuff, you weren't dependent on something that might break with an update of theirs. And you might well even want to package your own stuff, to help you keep track of dependencies between various components. Blastwave, Companion CD, and maybe even sunfreeware.com all tend to depend on core system packages and on their own packages, but not on one another's. So you'll probably end up with duplicates if you're using prepackaged software from different sources, at least until such time if any as there is a unified repository with overall consistency of dependencies, which in turn implies either a single updating authority or a very close level of cooperation to keep everything consistent. Some of the distros (like Nexenta in particular) may well "solve" this by effectively becoming the single authority or at least focal point for that sort of cooperation with regard to their repositories. I think many of us suppose that some future Solaris (Indiana seems to aspire to it) will also have a large repository that attempts to balance the competing interests of stability and remaining reasonably up to date. Don't assume this sort of thing is painless on other OSs - I've seen enough complaints to suspect that it isn't, although there's certainly room for improvement from what Solaris has historically done with this. This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
