First off, thanks for bumping bashburn. It's one of my favorite console interfaces to burning optical media. Now, for the problem: bashburn has, according to the sourceforge.net page, sprouted a new "abstraction layer", which involves the func directory. The ebuild, however, does not include the func directory in the copy statement (line 43 of the ebuild): mv {burning,config,convert,menus,misc,lang} ${D}/opt/BashBurn This results in bashburn not being able to resolve certain function names related to configuration, with messages such as: /opt/BashBurn/config/configure.sh: line 14: /opt/BashBurn/func/configfunc.sh: No such file or directory /opt/BashBurn/config/configure.sh: line 31: pretty_top: command not found Reproducible: Always
Created attachment 119138 [details, diff] Patch to add func directory to bashburn install image
Note: applying the fix in the patch made my installation configurable again.
Steve, you bumped this, please have a look.
Fixed in CVS, with beandog's consent (IRC)