diff --git a/devel/Makefile b/devel/Makefile index fe1701c773a0..ce9c86a1bf89 100644 --- a/devel/Makefile +++ b/devel/Makefile @@ -3556,6 +3556,7 @@ SUBDIR += rubygem-authlogic SUBDIR += rubygem-benelux SUBDIR += rubygem-bioruby + SUBDIR += rubygem-bugspots SUBDIR += rubygem-builder SUBDIR += rubygem-chronic SUBDIR += rubygem-classifier diff --git a/devel/rubygem-bugspots/Makefile b/devel/rubygem-bugspots/Makefile new file mode 100644 index 000000000000..189e56d127b5 --- /dev/null +++ b/devel/rubygem-bugspots/Makefile @@ -0,0 +1,25 @@ +# New ports collection makefile for: rubygem-bugspots +# Date created: 2012-01-11 +# Whom: TAKATSU Tomonari +# +# $FreeBSD$ +# + +PORTNAME= bugspots +PORTVERSION= 0.1.1 +CATEGORIES= devel rubygems +MASTER_SITES= RG + +MAINTAINER= tota@FreeBSD.org +COMMENT= Bugspots - Bug Prediction Heuristic + +RUN_DEPENDS= rubygem-grit>=0:${PORTSDIR}/devel/rubygem-grit \ + rubygem-rainbow>=0:${PORTSDIR}/devel/rubygem-rainbow + +USE_RUBY= yes +USE_RUBYGEMS= yes +RUBYGEM_AUTOPLIST= yes + +PLIST_FILES= bin/bugspots bin/git-bugspots + +.include diff --git a/devel/rubygem-bugspots/distinfo b/devel/rubygem-bugspots/distinfo new file mode 100644 index 000000000000..9427a67deb5f --- /dev/null +++ b/devel/rubygem-bugspots/distinfo @@ -0,0 +1,2 @@ +SHA256 (rubygem/bugspots-0.1.1.gem) = 8190d17f46a5b1af822e3ce86fb1182c8435bfb083d6b4ecfebbf1c33bbabe3e +SIZE (rubygem/bugspots-0.1.1.gem) = 7680 diff --git a/devel/rubygem-bugspots/pkg-descr b/devel/rubygem-bugspots/pkg-descr new file mode 100644 index 000000000000..1f5069660fbd --- /dev/null +++ b/devel/rubygem-bugspots/pkg-descr @@ -0,0 +1,15 @@ +Bugspots - Bug Prediction Heuristic + +An implementation of the simple bug prediction heuristic outlined +by the Google Engineering team: Bug Prediction at Google + + Well, we actually have a great, authoritative record of where + code has been requiring fixes: our bug tracker and our source + control commit log! The research indicates that predicting bugs + from the source history works very well, so we decided to deploy + it at Google. + +Point bugspots at any git repo and it will identify the hotspots +for you. + +WWW: https://github.com/igrigorik/bugspots