We noticed that BASH_COMPLETION_NAME will be ignored always and Zac told us about a filter for BASH_.* variables. "< zmedico> idl0r: oh, we have a blanket filter for BASH_.* because typically those are bash internals and it has issues with them being set" "< zmedico> I'd suggest not using variables that start with BASH_ :)" So we have to choose a new name, what about BASHCOMPLETION_NAME instead? The following packages are currently using this variable: app-office/openoffice app-portage/udept dev-libs/dbus-glib gnome-extra/gdesklets-core sys-apps/paludis And last but not least: vim.eclass
I agree, let's call it BASHCOMPLETION_NAME. If this is the whole list, let's just make the changes and reference this bug. I think it in non-evasive enough.
Fixed everything, thanks for the analysis and reporting.
Please excuse my ignorance. I already have openoffice-3.2.0 installed on my amd64 box. Does this mean I have to re-emerge the affected packages to use the new variable name?
(In reply to comment #3) > Please excuse my ignorance. I already have openoffice-3.2.0 installed on my > amd64 box. > > Does this mean I have to re-emerge the affected packages to use the new > variable name? > Not all. dev-libs/dbus-glib yes, not sure about sys-apps/paludis.