On Fri, Dec 21, 2007 at 04:32:23PM -0800, Chris Quenelle wrote: > I've got: > files/directories/links > relative pathname of each of the above > grouping of items into logical packages > dependencies between packages > all the extra per-product volume/product/config goop that gets shoveled > into SYSV packages that someone will just tell me. > > What else?
You might want to know what files are expected to change out from under the packaging system and which ones the packaging system is expected to own completely (i.e., e/v-type files vs f-type). We've discussed the idea of converting IPS packages to svr4 packages on the fly, too, so you could download a svr4 package from a url that happened to be served by an IPS depot. Something like that is quite low on our priority list, but if you'd be interested in implementing such a thing, I think we'd be happy to take it. That way, your packages could use IPS as the canonical format, and svr4 packages could be extracted as needed. However, I'm not sure that I'd want to do anything other than a 1:1 mapping between packages, so if you really want to "combine and split", then this is probably not your answer. Alternatively, I'm beefing up (and rationalizing) solaris.py, since we'll need to be doing svr4 -> IPS conversions for some time to come. I'm starting out with the same little descriptor language you see used in, say, src/util/distro-import/i386/SUNWckr, but there's no particular reason that it couldn't be coaxed to spit out svr4 packages as well as publishing to an IPS repo, if you thought that looked promising. I hope to be ready for a preliminary review early in January (though you or anyone else is welcome to look at it at any time, if you want). Danek _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
