The -b/--binlogs option for mydumper requires that mydumper be compiled with -DWITH_BINLOG=ON. This is not enabled in the 0.6.2 ebuild and is not exposed with a USE flag, and so --binlogs is not even optionally available without configuring the build by hand. I would suggest adding a USE=binlogs flag to enable this option. I don't have a patch to offer because I'm really not familiar at all with cmake.
It should be noted that mydumper-0.6.2 is pretty much moot at this time, the current release is 0.9.1
Would you use this feature Phil?
From https://github.com/maxbube/mydumper/issues/61: "DWITH_BINLOG=ON is deprecated and will be totally removed in some of the next releases. For binlog backups I would recommend to use mysqlbinlog > 5.6."
I *personally* have never used it for my own backups. I think I ran across it in the documentation and wanted to experiment with it, but couldn't because there wasn't a way to enable it. Right now, the principal problem with the dev-db/mydumper ebuild is that it is badly outdated. mydumper-0.6.2 has serious functional bugs, which are fixed in the current version 0.9.1. Among other issues, mydumper-0.6.2 cannot correctly back up VIEWs. I don't remember the other type of database object it does not correctly back up, but the end result is that you cannot successfully use mydumper-0.6.2 for complete, functional MySQL backups; it is necessary to use mysqldump to back up the schemas and mydumper to separately back up the table data. Looking at https://github.com/maxbube/mydumper/issues/61, it seems the -DWITH_BINLOG=ON issue is completely moot, but the ebuild does need to be updated for mydumper-0.9.1. I have my own local updated version of the ebuild, and can confirm that there are no ebuild issues and that mydumper-0.9.1 builds cleanly and works correctly.
(In reply to Phil Stracchino (Unix Ronin) from comment #4) > Right now, the principal problem with the dev-db/mydumper ebuild is that it > is badly outdated. https://github.com/gentoo/gentoo/pull/5873 Would you like to join maintaining the package via proxy maint? > Looking at https://github.com/maxbube/mydumper/issues/61, it seems the > -DWITH_BINLOG=ON issue is completely moot, but the ebuild does need to be > updated for mydumper-0.9.1. I have my own local updated version of the > ebuild, and can confirm that there are no ebuild issues and that > mydumper-0.9.1 builds cleanly and works correctly. So can this be closed as OBSOLETE?
I imagine so, but the ebuild should be updated to 0.9.1.
Closing this one. If you can, please test https://github.com/gentoo/gentoo/pull/5873. Thank you.
