command-not-found.pl: don't rely on Config.pm anymore #17715
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@domenkozar, thanks for your PR! By analyzing the annotation information on this pull request, we identified @edolstra and @nathan7 to be potential reviewers |
|
Hmm, this doesn't really work. |
domenkozar
force-pushed
the
command-not-found-perl-removal
branch
from
1fa6114 to
5638a43
Compare
|
Fixed! |
|
Wait, this is not |
|
I see now, Perl uses same arch syntax as we do: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As part of NixOS/nix#341, don't rely on perl Nix modules for command-not-found.
cc @edolstra