in reply to How do I package a module and related apps for successful upload to cpan

Update:

After some trial and error I discovered the root problem. I was trying to publish a distro whose name GHCN did not correspond to a module in the package; i.e. there was no GHCN.pm.

In hindsight the answer was in the PAUSE message.

Either someone else has ownership over that package name, or this is a brand new distribution and that package name was neither listed in the 'provides' field in the META file nor found inside the distribution's modules.

Obvious now, wasn't then. I was thinking of GHCN:: as a container for modules, but GHCN was not a sensible choice for the main entry point.

Once I figured that out, I decided that Fetch.pm would make a good entry point, and based on the other feedback I received here I decided to name the collection Weather::GHCN::Fetch.

Thanks again for your advice. It was most helpful.
  • Comment on Re: How do I package a module and related apps for successful upload to cpan

Replies are listed 'Best First'.
Re^2: How do I package a module and related apps for successful upload to cpan
by NERDVANA (Priest) on Sep 19, 2022 at 10:43 UTC
    While I agree that top-level GHCN was a bad idea, if it had been an appropriate name, you can always make a GHCN.pm which contains nothing but POD explaining the collection of modules. Or, create a top level module that does nothing but export sugar functions for working with the other objects in the collection.