Brock Pytlik wrote:
Bart Smaalders wrote:
Alan Coopersmith wrote:
However, once you have faceted packages, you'll also want these
dependencies
to only apply to specific facets, such as .h dependencies being used
when
you install the development facet but ignored if you don't. I know
Bart's
spent some time thinking about these - will your work tie into that
as well?
[1]
http://mail.opensolaris.org/pipermail/pkg-discuss/2009-March/011865.html
Indeed; facets are the right way to deal w/ "nice to have in case you
need it" portions of the package. It makes no sense to install the
components for which you don't have the dependencies installed, so
that bit that requires perl in Chris's example should be faceted
such that the dependency on perl is also faceted.
I'm curious, do we have any plan to allow for dynamic facet setting? To
continue with Chris's example, we could have a facet which was true/on
if perl was installed in the image the package was being installed into
and false/off if it's not. I think that's not a road we're planning to
go down, or even want to go down as I can see some unintended
consequences stemming from it. I'd thought I'd bring it up though and
see what people thought.
I'd really not like to go down this road, because the later
installation of perl will force a re-evaluation of all pkg dependencies
to see if any had such a dynamic facet; if that package had been
installed from CD or other repo it would block the addition of
perl to prevent a broken package state.
I'd much rather use facets to select optional components... we
do need to work on facet user interfaces, though.
- Bart
--
Bart Smaalders Solaris Kernel Performance
[email protected] http://blogs.sun.com/barts
"You will contribute more with mercurial than with thunderbird."
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
