On 11/23/10 02:04 PM, Keith Mitchell wrote: ...
For the CR I'm addressing in the install gate, one of the packages in question (system/library/install) has files that are delivered to usr/lib/python*, but those files were not analyzed as Python files until the shebang line was added (see CR 6999699). (In retrospect, I should have tarred up a sample set-up that pointed to usr/lib/python2.6/vendor-packages, but I think it should be easy to reproduce. I agree that there could be unintended side effects from "blindly" analyzing all .py files as python modules; I simply wanted to bring up feedback based on what I'd seen (admittedly perhaps a bit strongly worded).
As far as I can tell, simply delivering a python file (regardless of shebang line) to usr/lib/python* (where '*' is 2.6 as an example) should cause dependency analysis to be performed.
If you could find a specific case where a python file was being delivered there, but wasn't being analyzed, and has no shebang line, I think that would be an interesting case to dissect.
-Shawn _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
