Mike Gerdts writes: > > - What are the future needs that the package/patch system needs to > > address? > > Multiple installation databases per machine. I would really like to
+1 > > - What are the shortcomings of the current system? > > Somehow Sendmail and/or Apache keep finding their way into kernel > patches. Given that these tend to have remotely exploitable problems Though this is a *frequently* reported problem, I think that's out of scope. The issue there is that the team delivering those compiled bits -- not the source files themselves, but the objects in the packages -- has determined that there's something about the proper operation of those bits that requires a particular dependency (the KU is unfortunately not an unlikely target). That event has nothing to do with the packaging or patching system in use. That _same_ issue can occur _regardless_ of what sort of packaging system is used, and it's something you need to take up with the teams who produce those compiled bits. As you're talking about patches here, that'd be Solaris (only), and it'd be something to ask the support group within sun.com, not something to address as an issue for opensolaris.org. As much as we (sun.com) need a "why are my patches all stuck together" FAQ, I think it's out of scope for packaging on OpenSolaris. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
