in reply to Should my project be uploaded to CPAN as a module or an Application?

A big warning regarding uploading your code as it is right now to PAUSE/CPAN: your choice of package names will currently register you as trying to claim a very large number of top-level, lower-cased package names. This is not a good idea.

For example, https://github.com/gllore/App-SeismicUnixGui/blob/0.70_60/lib/App/SeismicUnixGui/geopsy/dinver.pm has package dinver;. This will claim the top-level package "dinver".

  • Comment on Re: Should my project be uploaded to CPAN as a module or an Application? (FIX PACKAGE NAMES FIRST)
  • Download Code

Replies are listed 'Best First'.
Re^2: Should my project be uploaded to CPAN as a module or an Application? (FIX PACKAGE NAMES FIRST)
by gllore (Acolyte) on Jul 16, 2022 at 05:29 UTC

    Thanks etj

    For example, would the following solution keep a lower-cased package at its corresponding low level?

    package App::SeismicUnix::geopsy::dinver;
[reply]
[d/l]
      That would be a very idiomatic and good solution.

      Zooming out a bit - I happened to notice that you have another repo which looks like the actual place where the real code lives. Is there a reason not to add the extra CPAN-able stuff to it rather than have this separate repo?

[reply]

      Thanks again for that last note

      Yes, many fine examples

      already exist in the CPAN e.g., PDL itself

[reply]

In Section Seekers of Perl Wisdom