FS#57172 - [gcc] untracked python pyc objects
Attached to Project:
Arch Linux
Opened by Earnestly (Earnest) - Saturday, 20 January 2018, 13:37 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Friday, 01 June 2018, 09:35 GMT
Opened by Earnestly (Earnest) - Saturday, 20 January 2018, 13:37 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Friday, 01 June 2018, 09:35 GMT
|
Details
I've noticed some .pyc bytecode which isn't properly tracked
by the gcc package.
/usr/share/gcc-7.2.1/python/libstdcxx/v6/__pycache__ /usr/share/gcc-7.2.1/python/libstdcxx/v6/__pycache__/__init__.cpython-36.pyc /usr/share/gcc-7.2.1/python/libstdcxx/v6/__pycache__/printers.cpython-36.pyc /usr/share/gcc-7.2.1/python/libstdcxx/v6/__pycache__/xmethods.cpython-36.pyc /usr/share/gcc-7.2.1/python/libstdcxx/__pycache__ /usr/share/gcc-7.2.1/python/libstdcxx/__pycache__/__init__.cpython-36.pyc Ideally these would be generated during packaging using something like `python -m compileall' to avoid as many untracked files in the filesystem. |
This task depends upon
Closed by Bartłomiej Piotrowski (Barthalion)
Friday, 01 June 2018, 09:35 GMT
Reason for closing: Fixed
Friday, 01 June 2018, 09:35 GMT
Reason for closing: Fixed
Comment by
Bartłomiej Piotrowski (Barthalion)
- Saturday, 27 January 2018, 19:09 GMT
Comment by Earnestly (Earnest) -
Saturday, 27 January 2018, 19:14 GMT
Comment by
Alexander Schnaidt (Namarrgon) -
Saturday, 27 January 2018, 19:18 GMT
That's hardly important unless user executed gcc as root, but I
will fix it for fake packaging quality points.
Thank you...
Users will inevitably run gcc as root even if not via makepkg.
DKMS is a popular example.