Created attachment 443764 [details] dev-util/mdds-1.2.1.ebuild When trying to emerge app-office/libreoffice-5.2.9999, the dependency dev-libs/liborcus-9999 fails during configure phase with the following error message: checking for MDDS... no configure: error: Package requirements (mdds-1.2 >= 1.2.1) were not met: Requested 'mdds-1.2 >= 1.2.1' but version of mdds-1.2 is 1.2.0 Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables MDDS_CFLAGS and MDDS_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. Reproducible: Always Steps to Reproduce: Add keywords for libreoffice-5.2.999 try to emerge libreoffice-5.2.999 Therefore, I would like to suggest to version bump the mdds ebuild (see attached file).
Thanks! Please only submit unified diffs (over the latest available ebuild) so any changes can be reviewed easily.
Do note though that neither 5.2.9999 nor 9999 require the use of dev-libs/liborcus-9999 at this point.
Created attachment 443806 [details] emerge.log output for emerge -pv "=app-office/libreoffice-5.2.9999"
Here is the diff of the ebuilds: diff -s /usr/portage/dev-util/mdds/mdds-1.2.0.ebuild dev-util/mdds/mdds-1.2.1.ebuild Files /usr/portage/dev-util/mdds/mdds-1.2.0.ebuild and dev-util/mdds/mdds-1.2.1.ebuild are identical I cannot confirm the last comment, because on my workstation (amd64, portage-2.2.28), I get the output for emerge -pv "=app-office/libreoffice-5.2.9999" as seen in the attachment.
Because liborcus-0.11.2 is not keyworded either, and portage has no clue about 'best practise' unmask, --autounmask goes straight to 9999. Does not reflect real dependencies.
ah, thanks, now I got your statement.
CommitDate: Sat Sep 17 21:32:12 2016 +0000 URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5e503dc1 dev-util/mdds: Version bump to 1.2.2
