Description of problem:
This is a proposal.
Right now python37, python35, python34, python33 packages are built with enabled "flatpackage" macro.
I would like that the test directory is separated as a python37-test package even when "flatpackage" enabled.
Because the test directory is maybe not used, right? And it occupies 48MB/93MB = more than 50% of the total size.
$ rpm -qf /usr/lib64/python3.7/test/
$ du -sh /usr/lib64/python3.7
$ du -sh /usr/lib64/python3.7/test/
I am fine that the modification is just updated to rawhide.
Version-Release number of selected component (if applicable):
I personally don't like this. The decision was made that those packages would be plan flat. Can you please bring this up in python-devel mailing list for more audience?
Alright. I sent email to the mailing list now.
If we split out -tests, why not the other subpackages? tkinter brings in all of X11, or whatever the graphical stack is nowadays -- and that's also huge, IIRC.
(But it's shared with other packages.)
While 48MB is not that much, a major use case involves having 6 of these interpreters installed. It does add up.
The other thing is that once we start optimizing this for space, people will deploy it in containers etc.
I don't think that 300 MB of unused tests is a deal breaker on a developer machine.
> The other thing is that once we start optimizing this for space, people will deploy it in containers etc.
> I don't think that 300 MB of unused tests is a deal breaker on a developer machine.
My machine has only 50 GB in the root partition including /usr directory.
I regularly have to clean files.
$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/fedora_unused--4--164-root 50G 42G 5.2G 89% /
/dev/mapper/fedora_unused--4--164-home 178G 66G 104G 39% /home
I am posting the same answer I gave at the mailing list:
"Hello Jun, That is actually a valid concern and testing with multiple python interpreters is not the most disk-space friendly use case.
However those packages were intended to be flat, the whole interpreter in one binary rpm. In my opinion it's the only pragmatic choice when you take into account the maintenance burden of so many interpreters.
Also if we split the tests to a subpackage I can imagine having requirements for splitting them up more in the future as well. Thus I would say that I wouldn't like to split them up and just keep them as it is.
I'd be open of course to other possible solutions/arguments."
Thus in this case I would call this a feature or something that I wouldn't fix. It sort of defeats the purpose of those packages and it increases the maintenance burden (that we already carry a lot).
Also as a side note, I had a similar issue with my root partition and I realized that mock was actually caching gigabytes of rpms in my root partition which made me symlink its folder to home. Maybe that could save some more space in the long run.
Overall I'm inclined to close this as WONTFIX.
Your opinion makes sense. I am fine to close this ticket with WONTFIX.
> Also as a side note, I had a similar issue with my root partition and I realized that mock was actually caching gigabytes of rpms in my root partition which made me symlink its folder to home.
Yeah, mock cache is big size.
And /var/cache/PackageKit too . I deleted the cache files.
Now I am moving the files on /usr/local and /opt to /home, making the symlink.
Thanks for the suggestion!
 PackageKit accumulate over 18GBytes of RPM packages in /var/cache/PackageKit/metadata and fill my root filesystem with unused RPM files
per comment 8 , closing this as WONTFIX.