- graphics/zathura: update to 0.4.3
- graphics/zathura-djvu: update to 0.2.9
- graphics/zathura-pdf-poppler: update to 0.3.0
rigoletto on Mar 1 2020, 6:36 PM.Authored by
Why the change in MASTER_SITE? The project home page, when clicking on downloads still links to the https://pwmt.org/projects/girara/download/girara-0.3.4.tar.xz URL, so why not follow what upstream does?
I completely agree on removing the www.madpilot.net "mirror" which I added some time ago to fix a temporary problem.
While working in some of the zathura-* ports the source files were missing (I can't recall which ones now) and that is why I discovered they moved to a GitLab instance. Then I assumed they will move completely at some point, and IMO this is a better idea to keep MASTER_SITES consistent among all zathura-* instead of be changing one by one when necessary.
The distfiles are different.
EDIT: zathura-pdf-mupdf and girara are keep the same distfile.
I have no problems for the parts the I am maintainer of.
Make sure you have contacted the other maintainers and have permission or they are actually timed out.
Not all maintainers are subscribed to phabricator, so I don't think the review emails are enough to make sure maintainers are informed.
Sorry for late.
I do not think all the USE_LDCONFIG bits are needed.
The USE_LDCONFIG knob is there when the port provides a shared library that other ports will need to link with, here, the .so are plugins, and they will be dlopen'ed on request.
The distfiles were not matching and when the upstream mirror is not available the port system grab from the copy in FreeBSD own infrastructure.
Some version ago I could fetch the source, created a bug report (update report) but the committer couldn't fetch it: see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216067
It is about the worst reason possible to make a change. portlint is a static lint tool, it has no clue about what you are doing, it just see stuff and tells you what it thinks you should do, but it very often gets it wrong.
Sync with HEAD.