The port broke in the beginning of February when upstream uploaded a new
pluginloader tarball to MASTER_SITES.
Since the tarball is unversioned and only contains prebuilt Windows binaries,
here's an attempt at explaining what happened (thanks to Grzegorz Junka for the
investigation):
- Pipelight seems to be really bad at communication. The "News" section on the
website says 0.2.8 is the latest version.
- The "Compile Pipelight" section says 0.2.8.1 is the latest version.
- 0.2.8.2 was tagged in BitBucket in October 2015 but was never announced
anywhere on the website, and the project does not seem to have a mailing
list.
- The pluginloader tarballs, which contain prebuilt Windows binaries for
Pipelight's src/windows directory, were not updated at the time 0.2.8.2 was
tagged (the SHA256 checksums match those in the 0.2.8.1 directory in
MASTER_SITES). This only happened in February 2016, which broke our distinfo.
Note that it is unclear why the pluginloader tarballs were not generated in
October, and since those are binary blobs it is still possible that they do not
correspond to their respective source files. In the future, it would be good to
build those binaries with our MinGW ports instead of relying on those blobs.
PR: 207210
Submitted by: Piotr Kubaj <pkubaj@anongoth.pl>,
Grzegorz Junka <list1@gjunka.com>
MFH: 2016Q2
- Support multiple values in *_OLD_CMD, i.e. we can now fix both "/usr/bin/python" and "/usr/bin/env python" at the same time
- Default *_OLD_CMD values are now always appended, so you don't need to specify them in individual ports
- Add lua support (depends on USES=lua)
- Add more default values, such as "/usr/bin/env foo" for python, perl, bash, ruby and lua
- Shebangfix now matches whole words, e.g. we will no longer (erroneously) replace "/usr/bin/perl5.005" with "${perl_CMD}5.005" (but "/usr/bin/perl -tt" is still (correctly) replaced with "${perl_CMD} -tt")
Note that *_OLD_CMD items containing spaces must now be quoted (e.g. perl_OLD_CMD=/bin/perl /usr/bin/perl "/usr/bin/env perl")
Update shebangfix usage according to new rules in many ports:
- Remove *_OLD_CMD for patterns now replaced by default
- Quote custom *_OLD_CMD which contain spaces
Fix shebangfix usage in many ports (irrelevant to infrastructure change):
- Remove redundant SHEBANG_LANG (no need to duplicate default langs)
- Remove redundant *_CMD (such as python_CMD=${LOCALBASE}/bin/python${PYTHON_VER} when USES=python is present)
- Never use *_OLD_CMD in REINPLACE_CMD matchers, these should always look for exact string
Approved by: portmgr (bapt)
Differential Revision: D3756
