mirror of
https://git.FreeBSD.org/ports.git
synced 2025-01-26 09:46:09 +00:00
Update to 1.1.2
- Update WWW Changes: https://github.com/gruis/pry-remote-em/blob/master/CHANGELOG.md
This commit is contained in:
parent
f329a54600
commit
66b26e0a1a
Notes:
svn2git
2021-03-31 03:12:20 +00:00
svn path=/head/; revision=545964
@ -2,7 +2,7 @@
|
||||
# $FreeBSD$
|
||||
|
||||
PORTNAME= pry-remote-em
|
||||
PORTVERSION= 0.7.5
|
||||
PORTVERSION= 1.1.2
|
||||
CATEGORIES= devel rubygems
|
||||
MASTER_SITES= RG
|
||||
|
||||
@ -11,15 +11,18 @@ COMMENT= Connect to Pry remotely using EventMachine
|
||||
|
||||
LICENSE= MIT
|
||||
|
||||
RUN_DEPENDS= rubygem-eventmachine>=0:devel/rubygem-eventmachine \
|
||||
rubygem-highline>=0:devel/rubygem-highline \
|
||||
rubygem-pry>=0.9<1:devel/rubygem-pry
|
||||
RUN_DEPENDS= rubygem-eventmachine>=1<2:devel/rubygem-eventmachine \
|
||||
rubygem-highline>=2.0<3:devel/rubygem-highline \
|
||||
rubygem-msgpack>=1<2:devel/rubygem-msgpack \
|
||||
rubygem-pry>=0.11<1:devel/rubygem-pry \
|
||||
rubygem-ruby-termios>=1.0<2:comms/rubygem-ruby-termios
|
||||
|
||||
USES= gem
|
||||
USE_RUBY= yes
|
||||
|
||||
NO_ARCH= yes
|
||||
|
||||
PLIST_FILES= bin/pry-remote-em
|
||||
PLIST_FILES= bin/pry-remote-em \
|
||||
bin/pry-remote-em-broker
|
||||
|
||||
.include <bsd.port.mk>
|
||||
|
@ -1,2 +1,3 @@
|
||||
SHA256 (rubygem/pry-remote-em-0.7.5.gem) = 5bb9aadce19d491d1b87e02384a18a819224651bea7c03b5baccc2140eeab139
|
||||
SIZE (rubygem/pry-remote-em-0.7.5.gem) = 20480
|
||||
TIMESTAMP = 1598175396
|
||||
SHA256 (rubygem/pry-remote-em-1.1.2.gem) = ddb2075af23e01538e9a9cff64e4ba19bfd1aca39979c938a42bb9682278b137
|
||||
SIZE (rubygem/pry-remote-em-1.1.2.gem) = 31744
|
||||
|
@ -8,4 +8,4 @@ It adds user authentication and SSL support along with tab-completion and
|
||||
paging. It's compatble with MRI 1.9, or any other VM with support for Fibers
|
||||
and EventMachine.
|
||||
|
||||
WWW: https://github.com/simulacre/pry-remote-em
|
||||
WWW: https://github.com/gruis/pry-remote-em
|
||||
|
Loading…
Reference in New Issue
Block a user