On 02/16/11 04:09 PM, Brock Pytlik wrote:
> I don't have any objection to doing a pkgmogrify that way, as long as you know
> you're building on quicksand. The idea of a manual override of resolution is
> an
> interesting one. I'd have to think about how it might compare in use to the
> "empty" file action (which wouldn't necessarily have to be a file action
> either). I'd be curious whether you'd want to set the manual override on each
> action which depended on libGL.so.1, or whether you'd want to be able to say
> once, in service/opengl/ogl-select, that it delivers libGL.so.1 in a
> non-traditional way.
>
> The advantage I see with the "empty" file action is that then you'd also get
> conflicting file errors if you were installing both ogl-select and another
> package which actually delivered var/run/opengl/lib/libGL.so.1.
Though as /var/run (or in new builds /system/volatile) is a tmpfs file system
mount point, pkg should probably error anyway if a package tries to lay down
files there.
Thinking about this some more though, I've reworked what I was doing to be on
much more stable ground, by simply putting those links into the opengl package,
but with attributes for pkgmogrify to strip those entries post-resolution but
pre-publication:
http://cr.opensolaris.org/~alanc/7015340/
This way I won't be depending on private details of the pkg depend resolution
attributes, and if/when an "empty" action RFE is integrated, I'd just change
org.opensolaris.nopublish=true to whatever attribute is needed for that.
--
-Alan Coopersmith- [email protected]
Oracle Solaris Platform Engineering: X Window System
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
