cpet/freebsd-ports
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
dd9941dc74
freebsd-ports/www/rubygem-protocol-rack/Makefile

21 lines
414 B
Makefile
Raw Normal View History

www/rubygem-protocol-rack: Add rubygem-protocol-rack 0.1.6 Protocol::Rack provides abstractions for working with the Rack specification on top of Protocol::HTTP. This would, in theory, allow you to run any Protocol::HTTP compatible application on top any rack-compatible server. WWW: https://github.com/socketry/protocol-rack
2022-08-31 07:21:21 -04:00
PORTNAME= protocol-rack
www/rubygem-protocol-rack: Update to 0.2.4 Changes: https://github.com/socketry/protocol-rack/commits/main
2022-09-10 08:54:04 -04:00
PORTVERSION= 0.2.4
www/rubygem-protocol-rack: Add rubygem-protocol-rack 0.1.6 Protocol::Rack provides abstractions for working with the Rack specification on top of Protocol::HTTP. This would, in theory, allow you to run any Protocol::HTTP compatible application on top any rack-compatible server. WWW: https://github.com/socketry/protocol-rack
2022-08-31 07:21:21 -04:00
CATEGORIES= www rubygems
MASTER_SITES= RG
MAINTAINER= sunpoet@FreeBSD.org
COMMENT= Implementation of the Rack protocol/specification
Add WWW entries to port Makefiles It has been common practice to have one or more URLs at the end of the ports' pkg-descr files, one per line and prefixed with "WWW:". These URLs should point at a project website or other relevant resources. Access to these URLs required processing of the pkg-descr files, and they have often become stale over time. If more than one such URL was present in a pkg-descr file, only the first one was tarnsfered into the port INDEX, but for many ports only the last line did contain the port specific URL to further information. There have been several proposals to make a project URL available as a macro in the ports' Makefiles, over time. This commit implements such a proposal and moves one of the WWW: entries of each pkg-descr file into the respective port's Makefile. A heuristic attempts to identify the most relevant URL in case there is more than one WWW: entry in some pkg-descr file. URLs that are not moved into the Makefile are prefixed with "See also:" instead of "WWW:" in the pkg-descr files in order to preserve them. There are 1256 ports that had no WWW: entries in pkg-descr files. These ports will not be touched in this commit. The portlint port has been adjusted to expect a WWW entry in each port Makefile, and to flag any remaining "WWW:" lines in pkg-descr files as deprecated. Approved by: portmgr (tcberner)
2022-09-07 17:06:12 -04:00
WWW= https://github.com/socketry/protocol-rack
www/rubygem-protocol-rack: Add rubygem-protocol-rack 0.1.6 Protocol::Rack provides abstractions for working with the Rack specification on top of Protocol::HTTP. This would, in theory, allow you to run any Protocol::HTTP compatible application on top any rack-compatible server. WWW: https://github.com/socketry/protocol-rack
2022-08-31 07:21:21 -04:00
LICENSE= MIT
www/rubygem-protocol-rack: Update to 0.2.3 Changes: https://github.com/socketry/protocol-rack/commits/main
2022-09-03 23:47:46 -04:00
RUN_DEPENDS= rubygem-protocol-http>=0.23<1:www/rubygem-protocol-http \
www/rubygem-protocol-rack: Add rubygem-protocol-rack 0.1.6 Protocol::Rack provides abstractions for working with the Rack specification on top of Protocol::HTTP. This would, in theory, allow you to run any Protocol::HTTP compatible application on top any rack-compatible server. WWW: https://github.com/socketry/protocol-rack
2022-08-31 07:21:21 -04:00
rubygem-rack>=1.0,3:www/rubygem-rack
USES= gem
USE_RUBY= yes
NO_ARCH= yes
.include <bsd.port.mk>
Reference in New Issue Copy Permalink