Created attachment 595564 [details] build.log.xz >>> Install media-gfx/inkscape-1.0_beta1 into /var/tmp/portage/media-gfx/inkscape-1.0_beta1/image >>> Working in BUILD_DIR: "/var/tmp/portage/media-gfx/inkscape-1.0_beta1/work/inkscape-1.0_beta1_build" ^M[0/6] Generating inkscape-version.cpp^M[1/6] Generating inkscape-version.cpp revision is fe3e306978, 2019-09-17 ^M[1/2] Install the project... -- Install configuration: "Gentoo" -- Installing: /var/tmp/portage/media-gfx/inkscape-1.0_beta1/image/usr/share/inkscape/doc/AUTHORS -- Installing: /var/tmp/portage/media-gfx/inkscape-1.0_beta1/image/usr/share/inkscape/doc/TRANSLATORS CMake Error at cmake_install.cmake:48 (file): file INSTALL cannot find "/var/tmp/portage/media-gfx/inkscape-1.0_beta1/work/inkscape-1.0_beta1_build/org.inkscape.Inkscape.desktop". FAILED: CMakeFiles/install.util cd /var/tmp/portage/media-gfx/inkscape-1.0_beta1/work/inkscape-1.0_beta1_build && /usr/bin/cmake -P cmake_install.cmake ninja: build stopped: subcommand failed.
the inkscape build system does not create the desktop file if USE="-nls" for inkscape.
My opinion: Unless you want to fix it in the build system, just drop USE nls if it does not work.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a4603d7c1dc746eb7b4b0170d5120ca5e5efb222 commit a4603d7c1dc746eb7b4b0170d5120ca5e5efb222 Author: Michael Orlitzky <mjo@gentoo.org> AuthorDate: 2020-02-21 15:49:50 +0000 Commit: Michael Orlitzky <mjo@gentoo.org> CommitDate: 2020-02-21 19:52:01 +0000 media-gfx/inkscape: disable the effects of USE=nls. The upstream build system is broken with USE=nls at the moment. Rather than drop the USE flag entirely (which might lead users to think that it's going away) this commit comments out the resulting -DWITH_NLS parameter that gets passed to the build system. Thus "USE=-nls" becomes a lie, but it should begin to work again once the upstream bug is fixed. There is a highly visible comment in the ebuild reminding the maintainers to check on the upstream bug periodically. Bug: https://bugs.gentoo.org/699658 Inkscape-bug: https://gitlab.com/inkscape/inkscape/issues/168 Package-Manager: Portage-2.3.84, Repoman-2.3.20 Signed-off-by: Michael Orlitzky <mjo@gentoo.org> media-gfx/inkscape/inkscape-1.0_beta2-r1.ebuild | 9 ++++++++- media-gfx/inkscape/inkscape-9999.ebuild | 9 ++++++++- 2 files changed, 16 insertions(+), 2 deletions(-)
Rather than temporarily making the USE flag a no-op, wouldn't it make more sense to force it on/off with package.use.force or package.use.mask?
(In reply to Andreas Sturmlechner from comment #2) > My opinion: Unless you want to fix it in the build system, just drop USE nls > if it does not work. I can only repeat myself: This is so *not* important to jump through hoops for it. Just clean it up.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=603609036f44f8da97ff6fc700778f1be1998955 commit 603609036f44f8da97ff6fc700778f1be1998955 Author: Mikle Kolyada <zlogene@gentoo.org> AuthorDate: 2020-06-06 21:11:25 +0000 Commit: Mikle Kolyada <zlogene@gentoo.org> CommitDate: 2020-06-06 21:17:24 +0000 media-gfx/inkscape: multiple bugfixes - use the other tarball which include extensions - enable nls unconditionally to bypass the buildsystem's bug Closes: https://bugs.gentoo.org/722112 Closes: https://bugs.gentoo.org/699658 Package-Manager: Portage-2.3.99, Repoman-2.3.22 Signed-off-by: Mikle Kolyada <zlogene@gentoo.org> media-gfx/inkscape/Manifest | 2 +- .../{inkscape-1.0.ebuild => inkscape-1.0-r1.ebuild} | 18 +++++------------- 2 files changed, 6 insertions(+), 14 deletions(-)
