Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • WriteMakefile accepts a EXTRA_META argument that just get appended to the end of the generated META.yml so you can use it as for example:

    EXTRA_META => q{
    resources:
        repository: svn://svn.versed.se/public/Perl/modules/JavaScript
    },

    • Eric, Alias, & claes

      This is good stuff. It's great that there's already a convention for it.

      Maybe a bookmarklet or greasmonkey script could bring this feature to the forefront.

      • Ask, and thou shalt receive: http://userscripts.org/scripts/show/31660 [userscripts.org]. Enjoy! :-)

        • Wow, that's frickin' sweet!

          I made /repository:\s+(\S+)/ case insensitive by adding the /i at the end: /repository:\s+(\S+)/i

          Cheers

          • Wow, that's frickin' sweet!

            *g* Thanks.

            [ //i ]

            Not a bad idea. I'll add it to the next iteration of the script!

          • From my reading, 'repository' is an official key in the standard, so shouldn't need to be case insensitive. Are there dists using 'Repository'?

            • Yes, Alias's example has 'Repository' instead of 'repository'

              http://search.cpan.org/dist/ack/ [cpan.org]

              As for being an official key, that may be true, but I can't think of a good case where TPTB would want to differentiate between a Repository: or repository: or rEpOsitOry: or whatever (so case insensitivity shouldn't hurt).

              • Hmm, either Andy was ahead of his time or not reading carefully enough.

                As for being an official key, that may be true, but I can't think of a good case ... so case insensitivity shouldn't hurt.

                Well, hash-lookups are case sensitive. If we're going to get into a case-insensitive-preserving behavior with META.yml, that could get frustrating really quick. And generally, with regard to standards: "couldn't hurt" ... will.

                • You're right, a hash lookup would be problematic.
                  Maybe we can help people out by issuing warnings about their META. Some things that could help:

                      1. A META validator
                      2. A standard way of generating META during the dist build/ship process

                  • 1. A META validator

                    That would make a fine cpan module... possibly a kwalitee point?

                    2. A standard way of generating META during the dist build/ship process

                    Well, M::B already does a lot of that. I suppose it either needs to provide validation on the meta_merge or a nicer way to specify such things (extracted from standard sections in the pod would be nice too.)