On Fri, Oct 10, 2008 at 10:07:50AM -0700, Jordan Brown wrote: > We're building SVR4 packages and then converting them into IPS.
"We" being your team, or the OpenSolaris folks converting the Solaris WOS? > That conversion requires that we have at least a stub IPS manifest (right?). Not really, but there's useful information that could be in the pkg(5) form of the package that cannot be (or is not) derived from the SVr4 form. > Modularity would suggest that we should keep the IPS data "near" the > point where we create the SVR4 packages, and somehow carry it through > the process to the IPS conversion. Sure. > One sensible way to do that would be to put it into the SVR4 package, as > an additional file (or files) that the SVR4 processing doesn't use. > That way we only need to carry around a single object, and in stream > form, a single file - the SVR4 package. You could do that, I suppose. > I suspect we'll do this regardless for our own sanity, but it seems like > the best way for it to be done would be for the IPS conversion process > to understand this convention and extract the IPS metadata from the package. It's not clear to me why the core importation process should grow to understand a non-standard package format. The WOS conversion is still going to have to know about all the packages from the consolidations who won't put this special file in, so we can't just rely on the new format. If you have a more specific proposal, feel free to flesh it out. I think that the folks who, in their spare time, have been looking at making the ON build spit out pkg(5) packages, have been looking at more or less the reverse process -- taking the richer pkg(5) metadata and building the SVr4 metadata files from that -- but their spare time has been limited, so I don't think prototyping has gone very far. Danek _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
