profiles/base: Remove COLLISION_IGNORE for Python compiled mods

Remove the obsolete COLLISION_IGNORE entries for compiled Python
modules.  Those entries were historically added to ease the migration
from python.eclass to python-r1 which involved taking ownership of
compiled module files.  Nowadays they are rather irrelevant given that
python.eclass is gone for a while, and protect-owned is the default.

Also, the Jython variant happens to have invalid syntax.

Closes: https://bugs.gentoo.org/663170

diff --git a/profiles/base/make.defaults b/profiles/base/make.defaults
index 01744a72fa90ad234fc458ff1df752eb893ff5a4..a0a1d4f977bae57a1ae16d2697e50433f707920c 100644 (file)
--- a/profiles/base/make.defaults
+++ b/profiles/base/make.defaults
@@ -135,10 +135,9 @@ PYTHON_SINGLE_TARGET="python3_6"
 # Michał Górny <mgorny@gentoo.org> (10 Aug 2013)
 # Moved from portage's make.globals.
 # 1) do not uninstall kernel modules and therefore allow replacing them,
-# 2) allow replacing unowned compiled Python modules (python-r1 migration),
-# 3) allow replacing unowned dropin.cache files (twisted-r1 migration).
+# 2,3) removed wrt bug #663170,
 # 4) protect /var/{run,lock} symlinks for bug 519620
-COLLISION_IGNORE="/lib/modules/* *.py[co] *\$py.class */dropin.cache"
+COLLISION_IGNORE="/lib/modules/*"
 UNINSTALL_IGNORE="/lib/modules/* /var/run /var/lock"
 
 # Andreas K. Hüttel <dilfridge@gentoo.org> (23 Aug 2013)