develooper Front page | perl.modules | Postings from April 2019

Re: PAUSE permissions clash between URPM and urpm [TVIGNAUD]

Thread Previous | Thread Next
Neil Bowers
April 25, 2019 22:06
Re: PAUSE permissions clash between URPM and urpm [TVIGNAUD]
Message ID:
Hi Thierry,

I’m one of the PAUSE admins. I emailed you back in August 2017 about an issue in PAUSE that we were hoping to resolve, and are looking to complete the resolution of very soon.

> I’m working through tidying up permissions conflicts that have been caused by the fact that PAUSE now consider package names case insensitively (due to case-insensitive filesystems, as on Windows and MacOS X). PAUSE doesn’t let these situations occur now, but we have some historical cases. I’m sorting these out so that we don’t need code in the toolchain for dealing with permissions conflicts.

We’re working on changes to PAUSE where if you have an indexing permission on “foobar", and then rename it “Foobar”, all permissions on “foobar” will be automatically changed to the equivalent permissions on “Foobar”. This will prevent various clashes that have happened over the years.

> You have first-come permissions on both URPM and urpm.

But only the “urpm” module appears in the CPAN Index.

The URPM module is one of just two modules in the URPM distribution. Presumably if someone was going to install this distribution from CPAN, they might want to run “cpan URPM” or similar? They can’t do that right now though, because URPM isn’t in the index. Are people more likely to install a linux package to install it though?

The urpm module is one of many modules in the urpmi distribution. That distribution doesn’t contain a urpmi module, so people can’t run “cpan urpmi” to install that distribution. The urpm module is listed in the CPAN Index. How likely is it that people might want to run “cpan urpm” to install the distribution?

Do you know how people are likely to install your distributions? Will they do it using a CPAN client, or using a linux package? Even if you believe most people will install from linux packages, we still want the most likely behaviour to work on CPAN as well.

The change that we’re going to make won’t stop you from having these two modules (urpm and URPM) in two different distributions, this only relates to indexing permissions, and thus which of the modules will appear in the CPAN Index.

Right now both of these modules aren’t in the CPAN index anyway, only urpm is indexed:
Only “urpm” is in the index, so someone can run “cpan urpm” to install the latest “urpmi” release.
But you can’t run “cpan URPM” to install its latest release.

Once our proposed change is released, then PAUSE would index whichever of URPM and urpm was most recently released. If you’d prefer that URPM is the module that’s always indexed, you could just ensure that the “urpm” module is never indexed. The easiest way for you to achieve this would be for you to add the following to the META_MERGE clause in Makefile.PL for that distribution:

        no_index => {
            package   => [ ‘urpm'],

Hopefully this would result in minimal impact on the end-user experience for people using your distributions. What are your thoughts on the above?


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