Re: When is it time to stop posting to CPAN?

Part of my daily routine is to check the metacpan recent page. ~~Often~~ On occasion the majority of new releases (since the previous day) seem to me like they're only going to be of interest/use to the author. Over the years this all adds up, everyone needs a hobby I guess. When reading a post/chatterbox conversation when someone starts talking about putting their pet project on CPAN, more often than not I can see no valid reason anyone would have for using what they propose. This isn't to say that CPAN is 'complete', or that people shouldn't add stuff, but given the modern cpan installers can pull things directly from github that this could be a more suitable place to host some pet projects.

Update: slight rewording, strike out above.

Update 2: Related perl.com regularly publishes a curated list of what's new on cpan articles.

Comment on Re: When is it time to stop posting to CPAN?

Replies are listed 'Best First'.
Re^2: When is it time to stop posting to CPAN? by tobyink (Canon) on Oct 11, 2020 at 20:57 UTC
Is there a good way in META.json or Makefile.PL for a project to indicate a dependency on a Github-only Perl module? Until there is, hosting projects only on Github has a big disadvantage. toby döt ink	[reply]
Re^3: When is it time to stop posting to CPAN? by Fletch (Bishop) on Oct 12, 2020 at 05:26 UTC
Not directly relevant but similar in concept prior art: there's a package for emacs which lets you install directly from the github repo rather than pulling from its official package repos (MELPA/ELPA) Quelpa. It more or less pulls the source and does the equivalent of a `make dist` then installs that. The cake is a lie. The cake is a lie. The cake is a lie.	[reply] [d/l]
Re^3: When is it time to stop posting to CPAN? by perlancar (Hermit) on Oct 12, 2020 at 08:26 UTC
Even if CPAN clients can as easily install from GitHub, I like the ease of which a CPAN mirror can be used offline. I do maintain private CPAN-like repositories for personal/work use and should probably "publish" there more often instead of to CPAN for things like these. But I do like the nice things the ecosystem gives me, e.g. RT and CPAN Testers.	[reply]
Re^4: When is it time to stop posting to CPAN? by marto (Cardinal) on Oct 14, 2020 at 07:54 UTC
"I do like the nice things the ecosystem gives me, e.g. RT and CPAN Testers" Github has 'issues' for rt, and allows the use of continued integration testing (free tiers exist for most OS IIRC) for cpan testers.	[reply]
Re^5: When is it time to stop posting to CPAN? by tobyink (Canon) on Oct 14, 2020 at 09:48 UTC
Re^6: When is it time to stop posting to CPAN? by hippo (Bishop) on Oct 14, 2020 at 10:17 UTC
Re^6: When is it time to stop posting to CPAN? by perlancar (Hermit) on Oct 14, 2020 at 11:34 UTC
Re^2: When is it time to stop posting to CPAN? by perlancar (Hermit) on Oct 12, 2020 at 08:45 UTC
As a side note, my monthly blog post series (such as this one) also began as a reaction to the "What's New on CPAN series" on perl.com, which I saw often missed some modules (granted, it's a curated list) as well as included some non-new modules. My blog posts get the data from MetaCPAN API, so it should not miss any new distribution, and they are 99% automated so the effort to create a new post is minimal and there's a higher chance that I can keep up doing it.	[reply]


Keep It Simple, Stupid
	PerlMonks