You are not logged in.
Why its included in package?
Offline
These are files destination to test if python works well. It is mainly used by the developer of python to tests the various components of python and to avoid regression. Why it is included in the package? I suppose because upstream intended it so.
Offline
I see. I was thinking about reporting it as "general gripe: it take hard disk space", but after a second though probably no one care.
Offline
I am personally against deleting files that upstream intended to be there. Even if it is not useful for you, it might be useful for someone else. I think Arch should stick to the general principle that we have what upstream ship.
Last edited by olive (2015-11-19 12:01:11)
Offline
I am personally against deleting files that upstream intended to be there. Even if it is not useful for you, it might be useful for someone else. I think Arch should stick to the general principle that we have what upstream ship.
Yes, I agree with you, but in some specific case, sometimes we need to trimmed down space as much as possible.
For example, currently I'm trying to build the smallest possible docker image using Arch Linux as base system. Many files which usually we don't care or need in desktop mode must be removed as much as possible. That is why I'm asking what is the use of files in directory test in /usr/lib/python2.7.
Offline
You can stop pacman installing that specific file if you prefer. Check out the NoExtract option in pacman.conf.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
olive wrote:I am personally against deleting files that upstream intended to be there. Even if it is not useful for you, it might be useful for someone else. I think Arch should stick to the general principle that we have what upstream ship.
Yes, I agree with you, but in some specific case, sometimes we need to trimmed down space as much as possible.
For example, currently I'm trying to build the smallest possible docker image using Arch Linux as base system. Many files which usually we don't care or need in desktop mode must be removed as much as possible. That is why I'm asking what is the use of files in directory test in /usr/lib/python2.7.
Then don't use arch at all, arch is not in any way optimised for disk space usage, we "waste" a lot of space by not splitting out -dev stuff, translations, building things with almost every feature enabled and so on.
Evil #archlinux@libera.chat channel op and general support dude.
. files on github, Screenshots, Random pics and the rest
Offline
Then don't use arch at all, arch is not in any way optimised for disk space usage, we "waste" a lot of space by not splitting out -dev stuff, translations, building things with almost every feature enabled and so on.
You get my point Mr. Elendig (which I presume that you have an experience building docker image with Arch too, and stumbled across image's size issue too).
This is where I would rant about "Why Arch is not splitting doc and dev files into separated package!!", but I bet you guys already has many discussion and debate about it, right?
Well, I love Arch, any other distro is not even an option, even if I am still jealous that Ubuntu can reach ~60M image size in docker hub [1] and Arch is stuck at ~100M [2].
[1] https://hub.docker.com/r/library/ubuntu/tags/
[2] https://hub.docker.com/r/base/archlinux/tags/
Offline
In pacman.conf
NoExtract = usr/share/doc/*
Now all doc files are gone...
Offline
This is where I would rant about "Why Arch is not splitting doc and dev files into separated package!!", but I bet you guys already has many discussion and debate about it, right?
Splitting the package too much can be a disadvantage too. Each times you want to develop/compile something you have to remind to install the dev packages. And if Arch begin to split other things too, each times you want to do something with a package, you must install the required component. And of course this is distro dependent. Many times you will find upstream doc saying: if <package> is correctly installed, you can do such and such things. it is nice that pacman -S <package> properly install the package and not a pacman -S <such> <and> <such> components that you have to figure out.
Last edited by olive (2015-11-20 11:38:03)
Offline
Mr.Elendig wrote:This is where I would rant about "Why Arch is not splitting doc and dev files into separated package!!", but I bet you guys already has many discussion and debate about it, right?
Evil #archlinux@libera.chat channel op and general support dude.
. files on github, Screenshots, Random pics and the rest
Offline