develooper Front page | perl.perl5.porters | Postings from February 2017

Re: Dropping conflicting PAUSE permissions

Thread Previous | Thread Next
Sawyer X
February 16, 2017 12:04
Re: Dropping conflicting PAUSE permissions
Message ID:

On 02/13/2017 11:22 PM, Neil Bowers wrote:
> Hi,
> Exec Summary: am I ok to drop PAUSE permissions
> on PerlIO::Scalar, PerlIO::Via, and VMS::stdio?
> I’m writing this wearing my PAUSE admin hat. I’m working through
> clearing up situations where people have permissions on package names
> that only differ in case. Most cases are where people have renamed a
> module, and not dropped the old permissions. Once we’ve resolved all
> these situations, we can tighten up PAUSE, and don’t need to have code
> to deal with various conflict edge cases.
> There are three pairs of module names where I’d like to drop the
> permissions on the no-longer-used name, where and if that’s possible.
> One of them is non-trivial.
> P5P has first-come permissions on both PerlIO::scalar
> and PerlIO::Scalar. The former is what’s now released with Perl 5 (and
> a bunch of people have co-maint on it as well), and the latter appears
> to have been released between 5.007003 and 5.008 (I’m looking at
> Module::CoreList).
> Similarly P5P has first-come on both PerlIO::via and PerlIO::Via. The
> former is what’s in use, and the latter was between 5.007003 and 5.008.
> *Question*: am I ok to drop the permissions on the no-longer used
> PerlIO::Scalar and PerlIO::Via?

I see no reason not to. Go for it.

And thanks for the research and analysis of this. :)
(And obviously, as always, the work you do!)


Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About