Summary: | [maintainer update] devel/ruby-build: update to 20141028 | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | Koichiro Iwao <meta> | ||||||
Component: | Individual Port(s) | Assignee: | Bartek Rutkowski <robak> | ||||||
Status: | Closed FIXED | ||||||||
Severity: | Affects Only Me | CC: | meta, robak | ||||||
Priority: | --- | ||||||||
Version: | Latest | ||||||||
Hardware: | Any | ||||||||
OS: | Any | ||||||||
Attachments: |
|
Created attachment 148783 [details]
20141028 has been released
A commit references this bug: Author: robak Date: Thu Oct 30 09:37:24 UTC 2014 New revision: 371728 URL: https://svnweb.freebsd.org/changeset/ports/371728 Log: devel/ruby-build: update 20140926 -> 20141028 PR: 194646 Submitted by: Koichiro Iwao <meta+ports@vmeta.jp> Approved by: mentors (implicit) Changes: head/devel/ruby-build/Makefile head/devel/ruby-build/distinfo Committed, thanks for your work! By the way, the next time you'll be sending PR with an update, please, consider correcting the PORTVERSION as described at the bottom of that document: https://www.freebsd.org/doc/en/books/porters-handbook/makefile-naming.html I just obey ruby-build's versioning. YYYYMMDD is upstream official version. Please see tags in repository. https://github.com/sstephenson/ruby-build/tree/v20141028 I meant I'm not using date instead of version number since upstream has no information. They uses YYYYMMDD as official version number. Should I have to use 0.0.yyyy.mm.dd in such case? |
Created attachment 148721 [details] patch subject describes all