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
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Bartłomiej Piotrowski (Barthalion)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

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
Comment by Bartłomiej Piotrowski (Barthalion) - Saturday, 27 January 2018, 19:09 GMT
That's hardly important unless user executed gcc as root, but I will fix it for fake packaging quality points.
Comment by Earnestly (Earnest) - Saturday, 27 January 2018, 19:14 GMT
Thank you...
Comment by Alexander Schnaidt (Namarrgon) - Saturday, 27 January 2018, 19:18 GMT
Users will inevitably run gcc as root even if not via makepkg. DKMS is a popular example.

Loading...