Commit Graph

20 Commits

Author SHA1 Message Date
sthen
533f76026d regen PLISTs following py-sphinx update 2022-10-31 08:47:46 +00:00
sthen
8311c389e4 regen PLIST following sphinx update 2022-07-07 16:23:17 +00:00
naddy
7a958849ed drop RCS Ids 2022-03-11 18:31:17 +00:00
daniel
7437f9d093 update py-sphinx to 4.0.2 and regen PLISTs for affected consumers
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
2021-07-06 16:55:32 +00:00
sthen
29704c3c83 adapt to py-sphinx-3.5.1 2021-02-20 22:27:27 +00:00
sthen
248932be74 switch MODPY_BIN_SUFFIX to -2 for py2 and (blank) for py3
switch ports using command-line tools from py-sphinx that don't need a
py2 version of it to py3-sphinx
2021-02-19 23:13:00 +00:00
daniel
ceb3a6300c update py-sphinx to 1.5.6
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@
2020-12-10 02:20:29 +00:00
sthen
a314fbcf4d unbreak databases/mydumper on LLD arches following mariadb update;
mydumper uses libm functions but doesn't pull in the library itself.
2019-08-07 09:06:11 +00:00
sthen
9fe1e38b23 replace simple PERMIT_PACKAGE_CDROM=Yes with PERMIT_PACKAGE=Yes 2019-07-12 20:43:27 +00:00
sthen
fb7f4374ad sync WANTLIB 2019-07-05 11:52:59 +00:00
shadchin
525cd9c2bd Unbreak after py-sphinx update to 1.4 2016-04-15 08:53:48 +00:00
giovanni
d423854a89 Update to 0.9.1 2016-03-03 10:01:09 +00:00
sthen
9005d1d063 sync WANTLIB 2016-01-17 17:29:07 +00:00
giovanni
9cd345e8f8 Update to 0.6.2
looks good to Brad
2015-10-27 10:51:32 +00:00
brad
fd4b0044b4 mydumper is tocuhing internal MySQL API it should not be. upstream has disabled
the binlog support until something can be done to fix it properly.

"The real problem here is that no application should ever include sql_common.h
or try to execute, the internal to libmysql functions, simple_command() or
advanced_command() directly.

The primary reason for this is that these functions are not safe for internal
API or structure changes and may cause applications crashes between even minor
versions of libmysql.a"

https://bugs.launchpad.net/mydumper/+bug/1316001

ok giovanni@
2014-09-15 17:10:45 +00:00
brad
b94a402501 Switch from using MySQL to using MariaDB attempt #2. MariaDB is a drop-in replacement.
ok sthen@
2014-09-13 18:09:20 +00:00
giovanni
8c0b60a890 Update to 0.6.1 2014-05-13 13:02:18 +00:00
naddy
2b8930a283 Drop USE_GROFF since groff and mandoc produce identical output. 2014-04-13 01:01:38 +00:00
giovanni
945364c5af enable man pages
tweak descr (from sthen@)
ok sthen@ benoit@
2013-09-25 09:02:08 +00:00
giovanni
952f68a3b9 mydumper is complement to mysqldump, for MySQL data dumping, providing
parallelism, performance and easier to manage output.

hints and ok sthen@ benoit@
2013-09-24 14:44:44 +00:00