Okay, the automatic bit of dependency tracking was what I was missing.
I bet resolving this has a lot to do with the extra 30 minutes build of
time that one of our engineers noticed (up from 1:20 to about 1:50 on a
Nehalem system.)
-- Garrett
On 03/ 6/10 07:40 AM, Alan Coopersmith wrote:
Garrett D'Amore wrote:
I'm looking at some of the packages in ON, and I don't see how
dependencies are properly tracked.
Specifically, the audio driver packages need to depend on driver-audio,
the driver-network-qfe package should have depended on
driver-network-hme. There are probably lots of others.
Admittedly I haven't upgraded to an IPS-ified ON nightly yet, but those
seem to be right in existing builds:
% pkg contents -o fmri -t depend driver/audio/audio810
FMRI
consolidation/osnet/osnet-incorporation
driver/[email protected]
Package building automatically inserts dependencies based on ELF "NEEDED"
sections, script #! lines, and a few other criteria. There are some
known bugs (following symlinks to a dependency) and open RFE's - and you
can always add manual dependencies for cases the automated one has little
hope of finding, like libraries you dlopen() or data files you open().
I've been planning to dig through the X apps someday to find out what
dependencies we should be manually listing for the fonts that clients
expect, for instance.
For the audio drivers, it looks like automation should be handling this:
% elfdump -d /kernel/drv/amd64/audio810
Dynamic Section: .dynamic
index tag value
[0] NEEDED 0x767 drv/audio
[1] NEEDED 0x771 misc/ac97
[...]
which "pkg contents driver/audio" shows are delivered there.
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
