diff options
Diffstat (limited to 'www/hs-http-reverse-proxy')
-rw-r--r-- | www/hs-http-reverse-proxy/Makefile | 23 | ||||
-rw-r--r-- | www/hs-http-reverse-proxy/distinfo | 3 | ||||
-rw-r--r-- | www/hs-http-reverse-proxy/pkg-descr | 6 |
3 files changed, 0 insertions, 32 deletions
diff --git a/www/hs-http-reverse-proxy/Makefile b/www/hs-http-reverse-proxy/Makefile deleted file mode 100644 index b612119d8f94..000000000000 --- a/www/hs-http-reverse-proxy/Makefile +++ /dev/null @@ -1,23 +0,0 @@ -# $FreeBSD$ - -PORTNAME= http-reverse-proxy -PORTVERSION= 0.6.0 -PORTREVISION= 2 -CATEGORIES= www haskell - -MAINTAINER= haskell@FreeBSD.org -COMMENT= Reverse proxy HTTP requests, either over raw sockets or with WAI - -LICENSE= BSD3CLAUSE - -DEPRECATED= Haskell libraries are getting pushed out of the ports tree. If you are using this port for development, consider switching to cabal sandboxes (old way), cabal new-build (new way), or use devel/stack. If you believe this port shouldn't be removed, contact haskell@FreeBSD.org -EXPIRATION_DATE= 2019-04-14 - -USE_CABAL= async blaze-builder>=0.3 case-insensitive>=0.4 conduit>=1.1 \ - conduit-extra data-default-class http-client>=0.3 \ - http-types>=0.6 lifted-base>=0.1 monad-control>=0.3 \ - network resourcet streaming-commons wai>=3.0 unliftio \ - wai-logger word8>=0.0 - -.include "${.CURDIR}/../../lang/ghc/bsd.cabal.mk" -.include <bsd.port.mk> diff --git a/www/hs-http-reverse-proxy/distinfo b/www/hs-http-reverse-proxy/distinfo deleted file mode 100644 index 27d4dd379fea..000000000000 --- a/www/hs-http-reverse-proxy/distinfo +++ /dev/null @@ -1,3 +0,0 @@ -TIMESTAMP = 1524852143 -SHA256 (cabal/http-reverse-proxy-0.6.0.tar.gz) = fb1c913111478384c4f23647810b8c3c01c79e9276a08a1ea46215e4a42dd1a8 -SIZE (cabal/http-reverse-proxy-0.6.0.tar.gz) = 10538 diff --git a/www/hs-http-reverse-proxy/pkg-descr b/www/hs-http-reverse-proxy/pkg-descr deleted file mode 100644 index bb89c68e4f74..000000000000 --- a/www/hs-http-reverse-proxy/pkg-descr +++ /dev/null @@ -1,6 +0,0 @@ -Provides a simple means of reverse-proxying HTTP requests. The raw -approach uses the same technique as leveraged by keter, whereas the WAI -approach performs full request/response parsing via WAI and -http-conduit. - -WWW: https://github.com/fpco/http-reverse-proxy |