|Welcome to the Monastery|
A more machine readable and "machine actionable" Changesby sedusedan (Monk)
|on Jun 11, 2014 at 04:43 UTC ( #1089476=perlquestion: print w/replies, xml )||Need Help??|
sedusedan has asked for the wisdom of the Perl Monks concerning the following question:
Not strictly related to Perl, because I want this to be useful outside the Perl toolchain too, but here it goes...
We already have the Changes file with its CPAN::Changes::Spec format standard (which I'm also using outside of Perl/CPAN distributions). What I'm trying to develop is something more machine readable and "machine actionable", for example:
One way to do this is to define more detailed specialized specification to the Changes entry, some of which have already been seen in practice. For example, if there is a group/heading called INCOMPATIBLE CHANGES, it means there are incompatible changes and the installer should confirm first. Likewise for #2, for example, we can define a group/heading called RESTARTED SERVICES or SERVICES TO RESTART (though this is arguably a misuse of the Changes file).
I am also aware that OS packages (like Debian's .deb, Redhat's RPM) deal with these installation/upgrade issues.
Any pointers/thoughts? I'd like to keep things simple and tend to just encode the required metadata/information into Changes, but I also don't want to end up with an overloaded and strange-looking Changes.
Back to Seekers of Perl Wisdom