On 2023-02-16 at 03:57, Maurizio Caloro wrote: > Hello > > i try to cleanup little me Debian 10.13, i thinking that have a zoo from > diffrent version from PHP running and in me opinion are same component > future running, in diffrent version, or ist this normal, you have this also > on your machine? > > ->like: common, xml, readline, bcmath, mysql, cli, gd, and so on. > > exist here the possibilites to filter, which are running, or not in use?
These are not different versions of PHP. They are different pieces of PHP functionality, so that you can install only the parts which you need for the programs etc. you want to run. > or it's this impossible?, then any programm has diffrent requirements. > > Setting up php7.4-common (1:7.4.33-5+0~20230214.77+debian10~1.gbpa1ea7f) ... According to 'apt-cache show php7.4-common': >> This package provides the documentation, examples and common >> module(s) for PHP. and it specifically means PHP 7.4. > Setting up php7.4-xmlrpc (1:7.4.33-5+0~20230214.77+debian10~1.gbpa1ea7f) ... Similarly, this one provides the xmlrpc module for PHP 7.4. > Setting up php7.4-curl (1:7.4.33-5+0~20230214.77+debian10~1.gbpa1ea7f) ... Similarly, this one provides the curl module for PHP 7.4. > Setting up php7.4-mysql (1:7.4.33-5+0~20230214.77+debian10~1.gbpa1ea7f) ... > Setting up php7.4-bcmath (1:7.4.33-5+0~20230214.77+debian10~1.gbpa1ea7f) ... > Setting up php7.4-imap (1:7.4.33-5+0~20230214.77+debian10~1.gbpa1ea7f) ... > Setting up php7.4-readline (1:7.4.33-5+0~20230214.77+debian10~1.gbpa1ea7f) > ... <snip> Et cetera. If you don't have anything installed that needs a specific module, then unless the package dependencies are written in a way that's more restrictive than I'd expect, you should be able to safely remove the specific module package(s) that you don't need. Figuring out why you have all these module packages installed is another matter. The most likely possibility is that you have some other package installed which lists them as a dependency, either a hard Depends or a soft Recommends. (Or you could have more than one.) In order to get started finding out which package(s) that might be, you could try something like: $ aptitude why php7.4-[modulename] However, this is not a 100% reliable method. For one thing, it will only list one possible dependency chain, and thus only tell you one "this is the reason" package; if you have more than one, it won't tell you that. There's also the second most likely possibility: that at some point in the past, you (or someone else with appropriate access to this system) explicitly told the package system to install these packages, possibly through the use of a wildcard. And of course it's impossible to initially rule out that there might be some non-packaged software installed (self-compiled, or installed from a tarball, or the like) that needs the modules; I don't know of any way to find that out other than to start removing modules and then waiting to see if anything breaks. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
signature.asc
Description: OpenPGP digital signature
