I think I remember that the core language modules will not update, but rather are updated as a separate package from cygwin.com (is this right?).
Like with many OS distros, Cygwin splits core Perl into two packages: perl and perl_base. I don't know what each provides. If you have both installed and you upgrade one, you should upgrade the other one too. Hopefully, that's automatic. Having core modules that don't match your perl would be a problem.
And what about the vendor modules?
Other Perl packages installed with Cygwin's package manager should have dependencies that forces their update when Perl is updated to something incompatible (a different major version). If not, just select to update all the Perl-related packages when you upgrade the core Perl ones. The package manager will make clear what's being updated.
And what about the vendor modules? But mostly, what about the modules in site_perl locations, modules I've built and installed myself?
Cygwin's package manager doesn't know anything about those, so it can't reinstall them for the new Perl. Fortunately, Cygwin appears to use versioned paths. So the modules that need reinstalling will simply vanish from perl's sight rather than malfunction.
For more control, use perlbrew.
In reply to Re: CygPerl question: what to expect from update when Cygwin releases 5.42
by ikegami
in thread CygPerl question: what to expect from update when Cygwin releases 5.42
by Intrepid
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |