Randy W. Sims wrote:
On 12/8/2003 9:23 AM, Graham Barr wrote:
On 6 Dec 2003, at 13:57, Randy W. Sims wrote:
=head2 meta-spec
Example:
meta-spec: <http://module-build.sourceforge.net/META-spec.html> - v1.1
I think it would be better to have the version number in the url. So someone with an old file can see what spec it conforms to.
[...]
Assuming we follow Stas' suggestion of storing the spec on CPAN and referring to it by a CPAN search URL (and I think we should), I see no way to reference an older version because of the way the search engine works. Search always brings up the latest version regardless of what you ask for. We could provide a direct link to the relevant version of the spec, but then we would need to also provide a link to the latest version somewhere.
Why do you need the link to the latest version in META.yml?
I guess the document itself can contain a link to the latest verrsion. Something like: The latest version of this document can be found at <http://search.cpan.org/~kwilliams/Module-Build/>.
Leaving off the version so search pulls up the latest.
...
I think embedding the name into the file is a bad idea from the maintenance point of view. But using the package's path should be just perfect. e.g.:
http://search.cpan.org/~WHOEVER/META.yaml-1.1/META-spec.html
Ok, I forgot about that syntax; I was thinking something like <http://search.cpan.org/search?query=Module-Build-0.18> which only pulls up the latest version even if you ask for a previous version.
That would mean, uploading META.yaml as a package with perl module versioning and Makefile.PL, so that search.cpan.org will arrange for the above URL.
The only thing to remember is that all versions must be kept on CPAN and not removed, if someone refers to an older version.
