The ebuild installs conf files in /etc/bcpp, but bcpp doesn't actually try to read them. Instead it searches the system path. (This is apparently a DOS relic) Here's a patch to bcpp.cpp which tries to read the conf file from /etc/bcpp. I would suggest applying it in the ebuild in the short term, and sending it upstream for the long term. Reproducible: Always Steps to Reproduce: 1.strace bcpp some-file.cpp 2>&1 | grep cfg 2.you will see it searching a lot of locations but not /etc/bcpp Actual Results: doesn't find the conf file, produces default-formatted output Expected Results: should have read the conf file that was supplied when bcpp was installed patch will be attached, to be located in /usr/portage/dev-util/bcpp/files/bcpp-20050725-etc-cfg-files.patch
Created attachment 160209 [details, diff] make bcpp try to read its conf file from /etc/bcpp/
Oh my - cpp team, any interest to maintain this little application. Otherwise forward assign to treecleaners, please.
Treecleaners, please consider this for removal.
Please don't remove it: it's useful
No sense in removing a working package that is usefull to someone. Patch applied and closing bug, thanks! (amd64 stable at the same time) (remove old version at same time) %% strace ./bcpp some-file.cpp 2>&1 | grep cfg open("bcpp.cfg", O_RDONLY) = -1 ENOENT (No such file or directory) open("/etc/bcpp/bcpp.cfg", O_RDONLY) = -1 ENOENT (No such file or directory)
