Tim Foster wrote: > It does mean that a random published manifest can't necessarily be used > as an example of packaging best practices
It already can't be, as we both practice and preach that manifests have the majority of their action attributes pkgmogrified into place, so as to cut down on redundancy. You also can't (or at least shouldn't) put pkg.size and pkg.csize attributes on your actions, nor elfhash, elfbits, etc. So I'd never recommend a published manifest as something to base a fresh, maintained manifest from. > I can certainly work on making pkgmogrify into a module once I've got > the sysrepo stuff out of the way. I'll file an RFE in the meantime. Sure. Implementation should wait until we're done implementing other features, as pipes should be sufficient in the meantime to implement the features we need. Danek _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
