Update to 0.2.

3 files changed, 13 insertions, 19 deletions

diff --git a/net/ruby-romp/Makefile b/net/ruby-romp/Makefile
index 257e47a901d7..49aca095e075 100644
--- a/net/ruby-romp/Makefile
+++ b/net/ruby-romp/Makefile
@@ -6,12 +6,9 @@
 #
 
 PORTNAME=	romp
-PORTVERSION=	0.1
-PORTREVISION=	1
+PORTVERSION=	0.2
 CATEGORIES=	net ruby
-MASTER_SITES=	http://rm-f.net/~cout/code/ruby/romp/ \
-		${MASTER_SITE_LOCAL}
-MASTER_SITE_SUBDIR=	knu
+MASTER_SITES=	http://rubystuff.org/romp/
 PKGNAMEPREFIX=	${RUBY_PKGNAMEPREFIX}
 DISTFILES=	${DISTNAME}${EXTRACT_SUFX} romp.html
 DIST_SUBDIR=	ruby
@@ -35,8 +32,7 @@ post-extract:
 .for f in romp.rb
 	${MV} ${WRKSRC}/${f} ${WRKSRC}/lib/
 .endfor
-	${CP} ${_DISTDIR}/romp.html ${WRKSRC}/
-	${RM} -f ${WRKSRC}/druby4*
+	${CP} ${DISTDIR}/${DIST_SUBDIR}/romp.html ${WRKSRC}/
 
 post-patch:
 	${RUBY} -i~ -pe 'sub /^(#include\s*<stdint\.h>)/, "/*\\1*/"' ${WRKSRC}/*.c
diff --git a/net/ruby-romp/distinfo b/net/ruby-romp/distinfo
index 2fb55cbe1e99..1921e9630f1b 100644
--- a/net/ruby-romp/distinfo
+++ b/net/ruby-romp/distinfo
@@ -1,3 +1,2 @@
-MD5 (ruby/romp-0.1.tar.gz) = 6ba0f76a799ad75581043b65cb53c86d
-MD5 (ruby/romp-0.1.tar.gz) = 89357a589a07068b5794b61280e78cac
+MD5 (ruby/romp-0.2.tar.gz) = 169eed3d3c4dddd4e852365369aee76e
 MD5 (ruby/romp.html) = IGNORE
diff --git a/net/ruby-romp/pkg-descr b/net/ruby-romp/pkg-descr
index 729a1952e23d..a4ce6b140ddc 100644
--- a/net/ruby-romp/pkg-descr
+++ b/net/ruby-romp/pkg-descr
@@ -1,22 +1,21 @@
 ROMP is the Ruby Object Message Proxy.  It is sort of like drb
 (distributed Ruby) in that it allows a Ruby client program to
-seamlessly talk to an object that is sitting on a server. However, it
-has many distinct advantages over drb:
+transparently talk to an object that is sitting on a server.  Its
+features include:
 
-- Much faster, up to 40000 messages per second (compare to 50 messages
-  per second for drb).
+- Up to 40000 messages per second
 
-- Allows more than one object to reside on the server; supports a form
-  for naming service for retriving references to objects.
+- Allows more than one object to reside on the server; supports a sort
+  for naming service for retrieving references to objects.
 
 - Fully thread-safe, provided the object sitting on the server is
   thread-safe.
 
-- Supports oneway calls, so the client does not have to block waiting
+- Supports one-way calls, so the client does not have to block waiting
   for a response from the server.
 
-- Allows exceptions to be propogated from server to client; massages
+- Allows exceptions to be propagated from server to client; messages
   the backtrace to make debugging easier.
 
-Author:	Paul Brannan (cout at rm-f.net)
-WWW:	http://rm-f.net/~cout/code/ruby/romp/
+Author:	Paul Brannan (paul at atdesk.com)
+WWW:	http://rubystuff.org/romp/