I noticed that the output of "pkg version" from my workspace wasn't what I
expected. Then I saw that setup.py was putting files into
proto/build_i386/lib.solaris-2.11-i86pc-2.4
rather than
proto/root_i386/usr/lib/python2.4/vendor-packages
as is typical for distutils-based installs. But it's not making it into
the real proto area. The test log file:
NOTE: Skipping ELF tests: No module named t_elf
NOTE: Adding
/export/home/dduvall/packaging/pgate/src/tests/../../proto/root_i386/usr/lib/python2.4/vendor-packages
to head of PYTHONPATH
NOTE: Adding
'/export/home/dduvall/packaging/pgate/src/tests/../../proto/root_i386/usr/bin'
to head of PATH
NOTE: Adding
/export/home/dduvall/packaging/pgate/proto/root_i386/usr/lib/python2.4/vendor-packages
to PYTHONPATH
NOTE: Adding '/export/home/dduvall/packaging/pgate/proto/root_i386/usr/bin'
to head of PATH
/usr/bin/python: can't open file
'/export/home/dduvall/packaging/pgate/src/tests/../../proto/root_i386/usr/lib/depot.py':
[Errno 2] No such file or directory
indicates that it's still trying to use the old proto area. Certainly the
pkgmk invocation is.
What's going on? Is there any way to be sure I'm testing the right bits?
The two warnings are also not so great, and the duplication of the PATH and
PYTHONPATH modifications should also be fixed.
Danek
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
