On Wed, 2011-02-16 at 09:21 -0700, Mark J. Nelson wrote:
> On 02/15/11 08:52 PM, Tim Foster wrote:
> > SUNW_PKG_HOLLOW
> >
> FWIW, I think this translates as "we need the pkginfo to be present so
> that package dependencies can be met in the nonglobal zones, but we
> don't want the actual software installed there." That would translate
> literally as "global zone variant tags on everything except for the
> legacy actions."
Right,
> A more generous (and appropriate, I think) approach would be the
> "global_zone_only_component" transform set in OS/Net, which allows
> header files, manpages, and mdb modules from such packages to be in
> nonglobal zones.
So users could certainly use pkgmogrify to apply such transforms after
running 'pkgsend generate'.
The 'svr4convert' prototype had a built-in pkgmogrify step and shipped a
set of standard transforms, but the feeling I got was that it was better
to separate pkgsend and pkgmogrify responsibilities (hence this webrev)
One good suggestion Bart had on IRC last night was to tag the package
with a pkg.send.convert.sunw-pkg-hollow attribute if the actions had
been generated from an SVR4 package that had SUNW_PKG_HOLLOW set,
leaving the decision to the user on how they'd like to further transform
the package, if at all.
An alternative approach would be to punt on the problem for now, and
have a follow-on putback automatically add appropriate
'pkg.linked.attribute.*' attributes to packages that came from SVR4
packages with SUNW_PKG_HOLLOW or SUNW_PKG_ALLZONES - though I'm not sure
yet how well this maps onto the linked-image work. Ed?
> This begs the question "should that transform set also set
> variant.opensolaris.zone=__NODEFAULT on legacy actions?"
I think it should.
cheers,
tim
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
