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
Module-Changes
More |
Login
| Reply
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
:-)
--Larry Wall in <1991May31.181659.28817@jpl-devvax.jpl.nasa.gov>
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Format of Changes.yml (Score:1)
What I came up with is a stream of yaml docs (separated by '---'), each containing a hash with info about that version. The reason to use a stream of separate docs is to cut back on indentation ("chrome"). So we only have one indentation level for the lists which means we can easily correct the format if somebody forgets to put the two spaces before the '- ' list token.
Below is an example of how a Changes.yml could loo
Re:Format of Changes.yml (Score:1)
I've seen your proposal and also thought about it.
It seems a bit too detailed. Also I don't think that splitting the structure into different YAML streams for the sake of indentation is ideal. I don't mind indentation - after all, it's supposed to be machine-readable.
If you really want a human-readable version as well, just have the YAML in Changes.yml and run:
changes -f Changes.yml -ff >ChangesBy the way, more updates are coming. I've simplified the YAML somewhat (less indentation!) and added a YAML validator that uses a schema with Kwalify.pm. v0.04 should be on CPAN soon.
Reply to This
Parent