|go ahead... be a heretic|
Understanding CPAN indexingby vsespb (Hermit)
|on Jul 16, 2013 at 12:31 UTC||Need Help??|
vsespb has asked for the
wisdom of the Perl Monks concerning the following question:
I have modules in my distributing, that I don't want to provide to end users. Actually I don't want to provide anything, except, probably, main module (App::MtAws), to end users, as my distribution is not a library, but a program, i.e. it is not for linking with other code.
The only thing should be available for end user is one script to be ran from command line, and some .pod in the future.
Examples of modules, I don't want to "provide" are: App::MtAws::Filter App::MtAws::GlacierRequest (total over 40).
here is the distribution
I have several issues with this.
1) I don't understand what different levels of "providing" a module exist. It seems that I don't want modules to be listed on CPAN pages, don't want it to appear in search, but I do want to "preserve" that namespace.
2) I have "no_index namespace" in my meta (both json and yml) (I've tried no_index directory also):
but it seems it doesn't work, because I see in my meta the following:
4) When I upload new, non-dev version to PAUSE, I am getting the following email shortly:
I believe this is because I previously used M:B version, which reported "version=0" for packages without version: example
and now I use M:B which reports no version in this case: example
Question is how to fix those emails and what else this issue affects in practice (except sending warning over email)?
5) I there a difference (in theory and practice) between