Garrett D'Amore wrote: > Ken Erickson wrote: >> >>> >>> The other issue is that integration into ON (with its more stringent >>> delivery requirements) may be more work than the project team >>> (whether Ken, Joerg, or other parties) is willing to take on. >>> However, doing the work now might simplify future matters, such as >>> making ufsdump/ufsrestore librmt aware. (Hmm... its even possible, >>> I suppose, that at that point it might be possible to do *that* >>> change with very little, or even no, ARC case work... just using >>> private APIs within ON.) >>> >>> -- Garrett >> We can do all that anyway, regardless of which consolidation delivers >> it, IMO. > > Uh, I'm not sure you can as easily get away with making > ufsdump/ufsrestore depend on librmt, at least not without either > upleveling the API or creating a Contracted Private interface with > associated contracts in place. Maybe I misunderstand? Given the dfifficulty of just getting the minimal amount of work approved, I don't think anybody will be in much of a hurry to do anything to ufsdump/ufsrestore. But if a contract interface is needed, it's not that big a deal. Certainly a lot less difficult than getting random open source to build within the ON framework (been there, done that).
> >> >> SFW is a much friendlier consolidation to work on open source with. >> Historically, the ARCs have not cared >> about which consolidation delivered something. Has this changed? > > I was just more thinking about weird cross-consolidation dependencies, > and pkghistory changes, etc. I prefer a simpler dependency graph > between consolidations, preferably one without cycles in it. :-) Its > not really an ARC issue, I suppose. Anyway, if it isn't something > that you or Joerg are interested in pursuing, then I guess it makes > little sense to worry about it. There really is only one dependency, which will be handled by a package dependency in SUNWrcmdr. pkghistory stuff will be taken care of by the RE build process like it always is - either implicitly or explicitly, if necessary. Again, much less to worry about that building open source as part of ON. Can't have cycles in the dependency graph - not allowed by the install process. You can't integrate packages that have cyclic dependencies. This scenario does not have them. -ken > > -- Garrett -- Ken Erickson | kene at Eng.Sun.COM Sun Microsystems, Inc., Solaris OS Engineering | Voice: (847)663-9471 4150 Network Circle MS UITA01 | Cell: (847)530-4603 Santa Clara, CA 95054 | If you want me to read something, don't send it as a StarOffice or HTML attachment.
