v3.5.0 breaks conf-perl-* package resolution on Windows
@smorimoto is already working on this.
Since Mar 29, 2026.
- Dominant language
- TypeScript
- Stars
- 228
- Forks
- 48
- Avg merge
- 15m
- Merged PRs (30d)
- 10
Description
conf-perl-ipc-system-simple and conf-perl-string-shellquote
(required by camlp5) have always required manual installation
on Windows. This worked fine through v3.4.8.
Since v3.5.0, two issues:
-
cpanmis no longer found in PATH:
Can't open perl script "/cygdrive/c/Strawberry/perl/bin/cpanm":
No such file or directory -
Even when installing modules via
curl cpanmin.us | perl,
opam verifies conf-perl-* using its internal Cygwin perl
(C:\.opam\.cygwin\root\bin\perl.exe) which has a separate
@INC from the perl where modules are installed. The check
always fails:
command: C:\.opam\.cygwin\root\bin\perl.exe -MIPC::System::Simple -e 1
@INC: /usr/local/lib/perl5/site_perl/5.40/...
Worked fine with v3.4.8. Current workaround: fetch cpanm via
curl and pin conf-perl-* to no-op packages.
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 comparing the Windows package-resolution behavior in v3.4.8 and v3.5.0, focusing on the cpanm lookup and the internal Cygwin Perl command shown in the report. Check the open pull request for the current direction; the issue is done when conf-perl-ipc-system-simple and conf-perl-string-shellquote resolve on Windows without the manual workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, perl, typescript
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100