Hi Maciej,
Am 29.08.2009 um 11:34 schrieb Maciej (Matchek) Blizinski:
On Sat, Aug 29, 2009 at 1:09 AM, Ben Walton<[email protected]>
wrote:
Excerpts from Sebastian Kayser's message of Fri Aug 28 16:30:43
-0400 2009:
Thanks for the feedback, regarding your concern I made an
adjustment. I
moved the .pyc,.pyo exclusion logic to gar.mk and it is triggered
when
PYCOMPILE is set.
This looks much better. Looking at the code though, I think you
should not that PYCOMPILE should be set to
/opt/csw/lib/python/site-packages/.*\.py for build descriptions that
don't set the category to python (since the MERGE_EXCLUDES use
addsuffix {c,o} with the value of PYCOMPILE. [This could maybe be
modified so that the trigger variable is separate from the variable
used to build the merge exclude rules...]
Since we are at the Python category - how about adding
/opt/csw/lib/python/site-packages/.*\.so to PKGFILES_RT?
Is this really useful? The runtime package collects stuff needed for
dependent apps excluding binaries and docs. I would imagine the
shared libs here are used for Python modules only which essentially
are py_* packages without runtime components.
Best regards
-- Dago
_______________________________________________
maintainers mailing list
[email protected]
https://lists.opencsw.org/mailman/listinfo/maintainers
