rexify --use "does_not_exist" does not give error message
Open
Nobody has claimed this yet.
bug
ready
- Dominant language
- Perl
- Stars
- 737
- Forks
- 214
- PR merge metrics
- No merged PRs in 30d
Description
When I tried to install a rex module using rexify --use Rex::Ext::Script, it gave me this output:
Getting dependencies for Rex::Ext::Script...
None found.
Getting perl dependencies for Rex::Ext::Script...
None found.
Downloading Rex::Ext::Script... done.
But nothing was in the lib directory. Turns out I wanted Rex::Ext::Stack, which installed correctly, but there was no error message about Rex::Ext::Script not existing.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing rexify --use Rex::Ext::Script and trace the command's module lookup and download handling, using the empty lib directory as the observed result. Done means a nonexistent module produces a clear error message, while a valid module such as Rex::Ext::Stack continues to install correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- perl
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100