HTTP::Thin is a thin wrapper around HTTP::Tiny adding the ability to pass in
HTTP::Request objects and get back HTTP::Response objects. The maintainers of
HTTP::Tiny, justifiably, don't want to have to maintain compatibility but many
other projects already consume the HTTP::Message objects. This is just glue code
doing what it does best.
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
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.
(Only the first 15 lines of the commit message are shown above )
Remove all := from BUILD_DEPENDS, here are never needed.
While there, cleanup, and sort depends.
When build and run dependencies are the same, there are three ways to
avoid duplicating the list while not adding the framework added
BUILD_DEPENDS to the RUN_DEPENDS. In order of preference, they are:
1) use RUN_DEPENDS to set BUILD_DEPENDS:
BUILD_DEPENDS= ${RUN_DEPENDS}
RUN_DEPENDS= foo:bar/baz
2) create another variable and use it:
MY_DEPENDS= foo:bar/baz
BUILD_DEPENDS= ${MY_DEPENDS}
RUN_DEPENDS= ${MY_DEPENDS}
3) use BUILD_DEPENDS to set RUN_DEPENDS and force evaluation:
BUILD_DEPENDS= foo:bar/baz
RUN_DEPENDS:= ${BUILD_DEPENDS}
Sponsored by: Absolight
HTTP::Thin is a thin wrapper around HTTP::Tiny adding the ability to pass in
HTTP::Request objects and get back HTTP::Response objects. The maintainers of
HTTP::Tiny, justifiably, don't want to have to maintain compatibility but many
other projects already consume the HTTP::Message objects. This is just glue code
doing what it does best.
WWW: http://search.cpan.org/dist/HTTP-Thin/
PR: 205362
Submitted by: amontalban@gmail.com
Approved by: mat (mentor)
Differential Revision: D4633
