I don't like having to execute perl-cleaner after an upgrade of perl. Is there a plan to get rid of this?
At least, gentoo bugzilla has two issues which aim to eliminate haskell-updater.
How can I get rid of perl-cleaner?
Message
How can I get rid of perl-cleaner?
Last edited by crocket on Tue Jan 28, 2020 11:46 pm, edited 1 time in total.
I submit that perl-cleaner is still very useful.
If you rebuild perl with ithreads that changes the perl environment directory path and without the aid of perl-cleaner quickly rebuilding only perl modules would not be possible without a larger effort.
I'd prefer to have this useful utility remain available somehow. If your running perl-cleaner after every perl update is that absolutely necessary? It shoudnt be unless the major version changes the perl environment directory path.
If you rebuild perl with ithreads that changes the perl environment directory path and without the aid of perl-cleaner quickly rebuilding only perl modules would not be possible without a larger effort.
I'd prefer to have this useful utility remain available somehow. If your running perl-cleaner after every perl update is that absolutely necessary? It shoudnt be unless the major version changes the perl environment directory path.
Compiling Gentoo since version 1.4
Thousands of Gentoo Installs Completed
Emerged on every continent but Antarctica
Compile long and Prosper!
Thousands of Gentoo Installs Completed
Emerged on every continent but Antarctica
Compile long and Prosper!
After every perl upgrade, I am prompted to run perl-cleaner. It actually removes garbages and notifies me of remaining garbages that I should eliminate manually.
I don't know why emerge cannot clean up garbages that perl leaves.
I just want upgrades to be effortless without having to run esoteric commands such as haskell-updater and perl-cleaner.
I don't know why emerge cannot clean up garbages that perl leaves.
I just want upgrades to be effortless without having to run esoteric commands such as haskell-updater and perl-cleaner.
I've never used haskell-updater.
Sometimes those post emerge build notifications can be accepted with a grain of salt.
Unless your getting errors caused by missing perl modules running perl-cleaner should be generally unnecessary.
perl-cleaner would be necessary or beneficial if the perl environment path ever changed due to a significant version upgrade or recompiling perl with USE=ithreads
Given i just did a world rebuild on my nas server for a global cflags alteration check this directory to view any existing perl library paths.
I've been compiling perl with multi threading support for over a decade and perl-cleaner has been a useful ally for post use flag alteration migration of existing perl modules.
Sometimes those post emerge build notifications can be accepted with a grain of salt.
Unless your getting errors caused by missing perl modules running perl-cleaner should be generally unnecessary.
perl-cleaner would be necessary or beneficial if the perl environment path ever changed due to a significant version upgrade or recompiling perl with USE=ithreads
Code: Select all
/usr/lib64/perl5/5.30.1/x86_64-linux-thread-multi/Given i just did a world rebuild on my nas server for a global cflags alteration check this directory to view any existing perl library paths.
Code: Select all
~ # ls -l /usr/lib64/perl5/
total 9
drwxr-xr-x 54 root root 128 Jan 24 23:14 5.30.1
drwxr-xr-x 4 root root 4 Dec 8 11:17 vendor_perl
I've been compiling perl with multi threading support for over a decade and perl-cleaner has been a useful ally for post use flag alteration migration of existing perl modules.
Last edited by ali3nx on Wed Jan 29, 2020 2:06 am, edited 5 times in total.
Compiling Gentoo since version 1.4
Thousands of Gentoo Installs Completed
Emerged on every continent but Antarctica
Compile long and Prosper!
Thousands of Gentoo Installs Completed
Emerged on every continent but Antarctica
Compile long and Prosper!
perl-cleaner may actually be unnecessary, but emerge still doesn't clean up garbages that perl leaves....
In particular, /usr/lib64/perl5/vendor_perl/x.xx.x/XML/SAX/ParserDetails.ini is a persistent son of a bitch.
Ideally, I want perl-cleaner to be absolutely unnecessary.
In particular, /usr/lib64/perl5/vendor_perl/x.xx.x/XML/SAX/ParserDetails.ini is a persistent son of a bitch.
Ideally, I want perl-cleaner to be absolutely unnecessary.
Last edited by crocket on Wed Jan 29, 2020 12:07 am, edited 2 times in total.
Why can't it? because aspects of perl are a pig ...
There use to be a similar need with python where you would need to run python-updater every time there was a new major version release ( viewtopic-t-1052610-start-0.html ). That went away with some effort from gentoo and aspects of buildability were refined.
Could perl and/or haskell benefit from a similar thing with single_target_perl_.... possibly but someone needs to product such a concept and upstream packaging needs to be manageable like this
There use to be a similar need with python where you would need to run python-updater every time there was a new major version release ( viewtopic-t-1052610-start-0.html ). That went away with some effort from gentoo and aspects of buildability were refined.
Could perl and/or haskell benefit from a similar thing with single_target_perl_.... possibly but someone needs to product such a concept and upstream packaging needs to be manageable like this
#define HelloWorld int
#define Int main()
#define Return printf
#define Print return
#include <stdio>
HelloWorld Int {
Return("Hello, world!\n");
Print 0;
#define Int main()
#define Return printf
#define Print return
#include <stdio>
HelloWorld Int {
Return("Hello, world!\n");
Print 0;
Perhaps, solving https://bugs.gentoo.org/456938 will free me from perl-cleaner? This is a very old bug. Unfortunately, I haven't learned perl.
At least, it seems I know what issues need to be solved to not need perl-cleaner.
At least, it seems I know what issues need to be solved to not need perl-cleaner.