commit: 0fcdbe8b3c7335397fc43fbdf1cd1091ffc84097
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Wed May 10 13:28:41 2017 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Tue May 16 17:11:30 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0fcdbe8b
python-utils-r1.eclass: python_moduleinto, clarify relative path use
Clearly indicate that python_moduleinto can be safely called outside
of the environment with Python interpreter established, and that
a single call can set the correct relative path for multiple different
implementations.
eclass/python-utils-r1.eclass | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/eclass/python-utils-r1.eclass b/eclass/python-utils-r1.eclass
index c46feb08449..c594cb46b5f 100644
--- a/eclass/python-utils-r1.eclass
+++ b/eclass/python-utils-r1.eclass
@@ -815,6 +815,12 @@ python_newscript() {
# When not set explicitly, the modules are installed to the top
# site-packages directory.
#
+# In the relative case, the exact path is determined directly
+# by each python_doscript/python_newscript function. Therefore,
+# python_moduleinto can be safely called before establishing the Python
+# interpreter and/or a single call can be used to set the path correctly
+# for multiple implementations, as can be seen in the following example.
+#
# Example:
# @CODE
# src_install() {
