Is there any customary way to put scripts on
CPAN? I've already put connect-tunnel
on CPAN, just like a module distribution, but I
wonder if that's the standard way to do it.
Wow, you mean people actually read the FAQ?:) I leave it in there as I keep hoping that it'll come back to life, but it's more likely that search will come to differentiate between a script and a module distribution and index them accordingly. For now, the FAQ is correct if a bit overly optimistic.
but search.cpan.org [cpan.org] is quite able to find activitymail [cpan.org], which is a complete distribution with a test suite, a META.yml, a MANIFEST and a bigger version number.
It's nice to be able to package a script through make dist, rather than just sending a bare file to PAUSE. This gives room for tests and examples. How would search.cpan differentiate a script from a module? Via the ME
Yes, if you package it like a distribution as I suggested, search will index it like a module but it will only show bits in the documentation section rather than in the modules section. There are plenty of distributions which contain scripts along with the modules.
This is the mostly right thing, but the metadata should provide more information for the indexing to make it more obvious and provide the end user with more information overall and not just for scripts v. modules. Yes, wouldn't it be nice...?
CPAN Scripts (Score:3, Informative)
Reply to This
well, I don't see why not as (Score:3, Insightful)
Reply to This
Re:well, I don't see why not as (Score:2)
Re:well, I don't see why not as (Score:2)
Re:well, I don't see why not as (Score:2)
Things do not work very well in the script section [cpan.org]. Take the first script for example:
It's nice to be able to package a script through make dist, rather than just sending a bare file to PAUSE. This gives room for tests and examples. How would search.cpan differentiate a script from a module? Via the ME
Re:well, I don't see why not as (Score:2)
This is the mostly right thing, but the metadata should provide more information for the indexing to make it more obvious and provide the end user with more information overall and not just for scripts v. modules. Yes, wouldn't it be nice...?
It has to be a single file? (Score:3, Informative)
OK, it's a quite straightforward system. That'll teach me to read the FAQ. :-S
The scripts have to be in a single file. So much for tests.
Reply to This