From 8cdd197ba643eb2608c5aab87567625bb9336cee Mon Sep 17 00:00:00 2001 From: David Stes <55844484+cstes@users.noreply.github.com> Date: Sun, 31 Mar 2024 18:41:25 +0200 Subject: [PATCH] opensmalltalk cog-spur: update to 5.0.3356 --- doc/building-and-packaging-faq.md | 17 ----------------- 1 files changed, 0 insertions(+), 17 deletions(-) diff --git a/doc/building-and-packaging-faq.md b/doc/building-and-packaging-faq.md index a34e194..a099ca5 100644 --- a/doc/building-and-packaging-faq.md +++ b/doc/building-and-packaging-faq.md @@ -22,23 +22,6 @@ <transform file path=.*\.py$ -> default pkg.tmp.autopyc false> ``` -## Why compiled python files are no longer automatically added to manifests? - -After introduction of Python 3.4 autopyc transform has to distinguish compiled files for python 2.x (*.pyc) and for python 3.x (__pycache__/*.cpython-3x.pyc). -This is done on the base of file path. -Files in usr/lib/python2.x/*.py are processed as earlier (following Python 2.x convention). -Files in usr/lib/python3.x are processed according to Python 3.x convention. -All other *.py files are not processed automatically. - -## How can I use COMPONENT_SUMMARY with PYVER components? - -There's a known oi-userland build system issue that COMPONENT_SUMMARY and other PKG macroses, containing spaces, can work incorrectly with PYVER components. -You can either specify such values in p5m file directly or use single quotation marks in Makefile, for example: - -``` -COMPONENT_SUMMARY= 'Cheroot - high-performance, pure-Python HTTP server' -``` - ## Why do I receive "mv: cannot access .deps/libsomething.Tpo" error during component build? The most frequent reason for this error is a regeneration of `Makefile.in` files in the wrong directory (when you used $(CLONEY) to populate build directory with sources and then run automake). -- Gitblit v1.9.3