Hi Neil, Go right ahead. I haven't touched the Qt4 code in a long time. Yes, Qt4 was meant to be a successor to Qt. The Qt bindings at this point are extremely old, I'd be surprised if anyone is still using them.
-Chris > On Nov 7, 2020, at 3:17 AM, Neil Bowers <neil.bow...@cogendo.com> wrote: > > > Hi Chris & Ashley, > > I’m one of the PAUSE admins. I’m working on resolving situations where there > are split and/or missing indexing permissions on CPAN distributions, and > where there is conflict between two or more distributions. These came about > historically for a number of reasons, including (1) packages were treated > case insensitively, but we then realised that caused problems, and (2) when > co-maints did releases, they’d get first-come on new packages, so you’d get > split ownership, and if one of the owners transferred, then it could become a > mess. > > Chris, you have both Qt and Qt4 on CPAN. Most of the permissions have been > dropped on the packages in Qt, and the contents of the two distributions are > similar enough that I suspect Qt4 was meant as a successor to Qt? If that’s > true, it looks like we could delete your Qt release from your author > directory, which will remove it from CPAN? There are some packages in the > index again the older release Qt4-0.60_b1.tar.gz which have no indexing > permissions. Deleting that release, and leaving just the latest release, will > clear up most if not all of the indexing permission issues on Qt. > > Ashley, some parts of your early releases of "Qt" are indexed, but it looks > like you then renamed your Qt distribution to be PerlQt, and PerlQt was > subsequently taken over by Germain Garand (GGARAND) — is that right? If so, > then we could delete the early releases of Qt from your directory, and > probably the early releases of PerlQt, since they’ve been superseded by > Germain’s releases. > > Are you both ok with me scheduling deletion of your old releases please? That > will resolve some if not all of the problems. If I go ahead, you’d both get > confirmation from PAUSE when I schedule the deletion, and the deletion itself > wouldn’t happen for 3 days (72 hours), so you have a chance to change your > mind as well. > > Thanks, > Neil
