Hi,
I'm trying to trace down an issue with our build process that is causing
one of the install packages, system/library/install, to not correctly
generate a dependency on lxml when using pkgdepend; while
install/installadm correctly generates the dependency on lxml.
I know that our make commands are rather cumbersome when it comes to
building the packages, so I've been trying to isolate and recreate part
of the commands to try and figure out where in the Makefile the issue is
stemming from, or if there's perhaps an issue with pkgdepend itself.
So far, I've been running pkgdepend (manually) against the pkgmogrified
manifests of each:
pkgdepend -m <pkg>.mog /path/to/ws/proto/root_i386 | grep lxml
When <pkg> is install-installadm.mog, the lxml dependency is found. When
<pkg> is system-library-install.mog, no lxml dependency is found. Both
mog files contain python file actions that import lxml (or lxml.etree)
in some fashion. In the case of system-library-install, it's all "from
lxml import etree"; for installadm it's that and "import lxml.etree" - I
thought that might have somehow confused pkgdepend, but modifying how
the files in system-library-install import lxml.etree did not change the
resultant dependencies.
At this point, I'm at a loss for how to continue; the man page for
pkgdepend doesn't list a "-v" option - is there any way to get more
verbose output or dig deeper into how pkgdepend is parsing these files
to figure out what might be going on here?
Thanks,
Keith
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
