require 'Plack', '1.0000', at => 'git://github.com/tokuhirom/Plack.git@deadbeef';
it's questionable whether it should support 'dev' option as well for search inclusion, but in most cases you should be able to specify the exact dev version such as:
require 'Plack', '1.0017'; # which is -TRIAL on CPAN
I thought, it's better than miyagawa/qahack-tokyo#6
because "at" or "via" do not depend on any VCS (git, svn, ...).
I want to rewrite my patch...
yeah that's true. however, there's a problem with the 'at' approach - it's ambiguous.
Sometimes there's a http: URL that "looks like" a git URL but maybe it doesn't. Or, there's a "@" somewhere in the URL which can be interpreted as a version spec, or maybe not.
'git', and 'rev' is very specific to git, but we can add 'svn' later.
I mean technically, you can create an HTTP-WebDAV based SVN url that looks like "http://example.com/foo.git".
URLs like firstname.lastname@example.org:foo/bar.git@commithash is very confusing, and cpanm only handles this with the heuristics (i.e. URL should end with .git). It is okay for cpanm's argument parser to be "smart" to handle it as the sanest way as possible, but for cpanfile spec, it's better to be explicit rather than implicit.
I see. It is difficult to identify VCS commands from only URL.
I also think so, "it's better to be explicit rather than implicit".
I didnt see any referenced commits has any progress been made on this issue yet?
Care to elaborate? Are they still in the plans to be included or are you taking a different direction?
Yes it will come hopefully soon.
Any news on this progress?
It's supported in the dev version of cpanfile and Carton, with at and git option.