Emerge install phase fails then building firebird-2.5.1 with "client" USE flag. ... install: cannot stat `*.msg': No such file or directory !!! doins: *.msg does not exist ... firebird-2.5.1 install phase completes well without flag. Reproducible: Always Steps to Reproduce: 1.Update Portage tree to recent state 2.USE="client" emerge firebird Actual Results: emerge install phase fails Expected Results: emerge process should complete successfully
Created attachment 302381 [details] emerge --info firebird
Created attachment 302385 [details] emerge build log
Yes this is more an experimental use flag. I was trying to build the bare minimum for client install. But you end up having to build and install so much, like the msgs file/database. Its really not worth it I don't think and will likely remove the use flag unless upstream makes modifications to make it more friendly. Probably should have added a warning on the client use flag. I changed the order of the install of the message files. Then realized they weren't even being built. Interesting it took this long for a bug report, expected one a long time ago :)
(In reply to comment #3) > Probably should have added a warning on the client use flag. I changed the > order of the install of the message files. Then realized they weren't even > being built. Interesting it took this long for a bug report, expected one a > long time ago :) Can you please submit a new ebuild, w/o this issue, to the latest version can get stabilzied to fix bug 240988
For the time being the client use flag could always be removed, which would correct this issue. Till I have a chance to work out the issues. The rest of the conditionals based on the use flag can remain, I believe. Just remove the use flag from the available use flags for the ebuild, so it can be stabilized.
Ok, I just mask the use flag. +# Michael Weber<xmw@gentoo.org> (02 Jun 2012) +# Not fit for production (bug 404403, comment #5) +dev-db/firebird client +
