https://bugzilla.suse.com/show_bug.cgi?id=1230448 https://bugzilla.suse.com/show_bug.cgi?id=1230448#c3 Thorsten Kukuk <kukuk@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(jbohac@suse.com) --- Comment #3 from Thorsten Kukuk <kukuk@suse.com> --- (In reply to Jiri Bohac from comment #2)
It used to be copied to the dump directory, alongside the vmcore, for potential users of a flattened-format vmcore that don't have makedumpfile installed. This is now mostly useless because the crash utility itself can use the flattened-format vmcore. Customers just copying the vmcore to us for analysis also don't need it. So kdump no longer copies it to the dump directory.
Ok, if I understand you correctly, we don't use this script anymore. Which means for me we could drop it?
And even if it did - it was not meant to be run on the system where it was installed, but on the system where the vmcore was analyzed. The system where it is installed also has the makedumpfile binary so it can be used instead.
If the script is not meant to be run on the system where it was installed, it should not be installed into /usr/bin but maybe /usr/share/makedumpfile/ or something similar.
So there is no reason to keep perl because this script is installed.
If the script is installed, RPM will generate a dependency on perl, so you cannot remove perl. I see two options here: 1. if the script is no longer needed, remove it 2. if the script should stay, move it to /usr/share/... and make mode 644, so that no perl dependency is created by RPM. -- You are receiving this mail because: You are on the CC list for the bug.