> Following the review here: > > https://trac.macports.org/ticket/33889 > > How should the port group use a git hash for determining which version > to download? Some features that would be nice: > > 1) ability to send a hash for the version to download (without having > git as a build dependence); this would make it possible to cache the > download as opposed to cloning every time
I think the git.branch can be used interchangeably: it's both a tag or a hash.
> 2) using the rss for livecheck (allows only checking the newest commit
> hash via the regexm command)
I think setting livecheck.url to the RSS file and livecheck.regex to an
appropriate pattern should suffice.
> 3) uniform versioning
>
> For (3), I prefer ${last_known_version}-${date} but don't mind
> changing this to something else as long as it's consistent.
I think it's acceptable as long as its not HEAD and it works for the
maintainer. It could be an incrementing number, it can be a date, it can be
some version/date combo like you suggest. For PSPP-devel I use
${version}-g${git.branch}.
> Open question: what to do about projects that never version? Assign a
> dummy version? Stick with just date?
Up to the maintainer. No harm in doing your suggestion for 3 above.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
