Hi Steve,

Back in February 2017 I emailed P5P about dropping the VMS::stdio shim (leaving 
VMS::Stdio in place) and dropping the PAUSE indexing permissions on VMS::stdio, 
leaving the permissions on VMS::Stdio in place:
    https://www.nntp.perl.org/group/perl.perl5.porters/2017/02/msg242988.html

I submitted a patch for the change in July or August that year, and the first 
stable release without VMS::stdio was 5.28. I then dropped the indexing 
permissions on VMS::stdio.

PAUSE currently has a “feature” where if you release Foobar and later you 
release foobar, you’ll end up with first-come permissions on both of them. This 
meant that the permissions on VMS::stdio reappeared (see 
https://github.com/andk/pause/issues/265) when a subsequent release of 5.26 
(which still includes VMS::stdio) was made.

Andreas and Rik will shortly be releasing a change in PAUSE behaviour: if you 
have first-come on foobar and then release Foobar, all permissions on foobar 
(not just yours) will be changed to equivalent permissions on Foobar.

Ahead of that I’ve dropped all permissions on VMS::stdio again.

Ilmari said that there’s a chance there might be another 5.26.x release, and if 
there were it would be done by you. Such a release would mean that the 
VMS::Stdio permissions would get switched to being VMS::stdio until the next 
5.28 release.

This probably won’t cause any problems anywhere in the toolchain, but if there 
is (going to be) another 5.26 release, could you let me know please? :-)

Thanks,
Neil

Reply via email to