all consumers were packaged and installed on amd64 by me; all python2
syntax in consumers appears to have been updated at this point making
it possible to move to the 4.x series.
lang/ghc bits look ok to gnezdo@
ok sthen@ on the rest
main changes are:
- add a new dep on py-requests
- undo the no longer needed iftex.sty workaround
- move MODPY variables to more standard location
- regen plist
Unfortunately py-sphinx changed the suffix from .txt to .rst.txt in the
1.5 series. This means we have to update PLISTs for about 20+ ports as
a result of this version update. Hopefully future updates of py-sphinx
won't be quite as involved.
ok sthen@
Release 1.4 of py-sphinx made this dependency optional. So adapt the port
to match. Instead we add a BUILD_DEP on py-sphinx_rtd_theme to the 3 ports
that actually depend on it. This may make updating py-sphinx_rtd_theme a
bit easier to update in the future as fewer consumers would need testing.
ok kmos@, sthen@
This update was submitted by Aisha Tammy as part of the batch of diffs
to get py-sphinx updated. However updating the rtd theme port also requires
regenerating packing lists for these consumers of py-sphinx:
devel/luacheck
devel/py-virtualenv
productivity/vdirsyncer
Luacheck is a static analyzer and a linter for Lua. Luacheck detects
various issues such as usage of undefined global variables, unused
variables and values, accessing uninitialized variables, unreachable
code and more. Most aspects of checking are configurable: there are
options for defining custom project-related globals, for selecting set
of standard globals (version of Lua standard library), for filtering
warnings by type and name of related variable, etc. The options can be
used on the command line, put into a config or directly into checked
files as Lua comments.
Luacheck supports checking Lua files using syntax of Lua 5.1, Lua 5.2,
Lua 5.3 and LuaJIT 2.0. Luacheck itself is written in Lua and runs on
all of mentioned Lua versions.
