[Slackbuilds-users] Duplicate perl-Tidy builds

[B. Watson]

On Thu, 5 Nov 2026, Mab974 wrote:

> I suppose that originally we hesitated between the Perl-Tidy program and
> the perl-Perl-tidy module. I sometimes have trouble with this rule:
> perl-Mojolicious could lead us to name perl-Minion and perl-Dancer2. What
> does the prefix perl- mean exactly? Should this slackbuild be named
> Perl-Tidy, based on CPAN ?

Nobody ever explicitly made a rule, so peoples' interpretations vary.

One way to look at it would be:

- always prefix with perl-
- add the CPAN name, with any :: turned into -

...which is how we arrived at perl-Perl-Tidy.

A variant of that: use the lowercased form of the CPAN name. If I had
been the one to submit that build, it would likely have been called
perl-tidy or (maybe, doubtfully) perl-perl-tidy, because I always
hated MixedCase in package names...

Whoever came up with "perl-Tidy" probably decided it seemed redundant
to use "perl-Perl-Tidy" or "perl-perl-tidy".

If I were starting from scratch and inventing a rule *now*, I might
say that all builds whose source comes from CPAN should be called
cpan-* instead of perl-* (since perl/ is already the category). But,
too late to change it now, more work than it would be worth, if indeed
it's worth anything at all.

The script I posted earlier (perlupd) tries to guess the SBo names,
based on the CPAN names, but it cheats a little by having a short list
of hardcoded names that don't fit the pattern.