New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
plenv rehash is so slow #81
Comments
Hm. But how do I detect these files? |
Why do you have to regenerate symlinks again? Can't you just have a disclaimer: I am newcomer to this topic, please forgive me if I am missing the context. |
@kazuho they are not symlinks. |
I'm sure you can reproduce this on your env, but in case it isn't here's what it loos like:
Because these commands exist for each perl, these shims are generated to keep track of the aggregated bin files. However this executable conflicts with plenv/perlbrew in the first place (they're there in I don't know what is the right thing to do, but an easy patch would be just ignore files that are a) known to come with perl core and b) ends with |
Actually, i was about to go ahead and delete all these
It is fairly annoying, and I wonder if there's a perl build option to disable them in the first place... |
That being said, this whole plenv commands including this unless i'm stupid, what I've found out so far is that bash for loop is so slow. I have 3716 bin files across various perl versions I have,
and just iterating them over in at this point i'm fairly convinced that I should just uninstall these dev versions and call it a day :/ |
plenv rehash
is so slow (takes about 10 seconds) as I have many plenv versions installed.rbenv rehash
is about 300ms.It annoys the hell out of me because
plenv install-cpanm
adds a rehash hook for every invocation for cpanm, even for--info
usage etc.Turns out there're lots of shims like
xsubpp5.20.1
, and that is causing the extra step.These executables are completely useless because plenv takes care of switching versions.
I'm sure if plenv stops symlinking these executables
plenv rehash
is much faster.The text was updated successfully, but these errors were encountered: