The bash environment filtering script is not catching all variables. It appears to miss the ones that have declare statements without a value. See below: $ echo declare -r PORTAGE_BINPKG_DIR="blah" | /usr/lib64/portage/bin/filter-bash-environment.py PORTAGE_BINPKG_DIR $ echo declare -r PORTAGE_BINPKG_DIR | /usr/lib64/portage/bin/filter-bash-environment.py PORTAGE_BINPKG_DIR declare -r PORTAGE_BINPKG_DIR $ emerge --version 2>/dev/null Portage 2.2_rc33-r4 (unavailable, gcc-4.3.2, glibc-2.9_p20081201-r2, 2.6.31-gentoo-r6athlon64x2_2009.05.31 x86_64) I am using tommy's portage-multilib branch of portage (but filter-bash-environment.py seems to be faithful to mainline portage). This bug causes the following error to be printed in my modification to portage-multilib. I had used filter_readonly_variables to try to avoid the following error/warning message: ``/var/tmp/portage/dev-lang/perl-5.10.1/temp/environment.amd64: line 117: declare: PORTAGE_BINPKG_FILE: readonly variable''
Created attachment 218029 [details, diff] handle declare -r without assignment
(In reply to comment #1) > Created an attachment (id=218029) [details] > handle declare -r without assignment Via gitweb: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=3a4a9cad036abf3f011b223fd6fb2fdf9649e213 This should have been released between 2.1.8 and 2.1.8.3.
