pwd /usr/share/octave patrizio@blight octave $ grep portage * ls-R:/var/tmp/portage/octave-2.1.69/image//usr/share/octave: ls-R:/var/tmp/portage/octave-2.1.69/image//usr/share/octave/2.1.69: ls-R:/var/tmp/portage/octave-2.1.69/image//usr/share/octave/2.1.69/imagelib: ls-R:/var/tmp/portage/octave-2.1.69/image//usr/share/octave/2.1.69/m: ls-R:/var/tmp/portage/octave-2.1.69/image//usr/share/octave/2.1.69/m/audio: ls-R:/var/tmp/portage/octave-2.1.69/image//usr/share/octave/2.1.69/m/control: ls-R:/var/tmp/portage/octave-2.1.69/image//usr/share/octave/2.1.69/m/control/base: ls-R:/var/tmp/portage/octave-2.1.69/image//usr/share/octave/2.1.69/m/control/hinf: ls-R:/var/tmp/portage/octave-2.1.69/image//usr/share/octave/2.1.69/m/control/obsolete: ls-R:/var/tmp/portage/octave-2.1.69/image//usr/share/octave/2.1.69/m/control/system: ls-R:/var/tmp/portage/octave-2.1.69/image//usr/share/octave/2.1.69/m/control/util: ls-R:/var/tmp/portage/octave-2.1.69/image//usr/share/octave/2.1.69/m/deprecated: ls-R:/var/tmp/portage/octave-2.1.69/image//usr/share/octave/2.1.69/m/elfun: ls-R:/var/tmp/portage/octave-2.1.69/image//usr/share/octave/2.1.69/m/finance: [CUT] the portage temp dir is remembered. this makes some ebuilds like octave forge be wrong. infact octave forge installs in /var/tmp/portage/octave-2.1.69/.... and this is a bug! i'm not sure...but there should be another file like ls-R that keeps the portage temp path. it's simple to check with sed and replace before merging. same bug with 2.1.6* please check
i remembered the other path maybe in subdirs too! cd /usr/libexec/octave/ root@blight octave # ls 2.1.64/ 2.1.69/ ls-R site/ root@blight octave # grep portage * ls-R:/var/tmp/portage/octave-2.1.69/image//usr/libexec/octave: ls-R:/var/tmp/portage/octave-2.1.69/image//usr/libexec/octave/2.1.69: ls-R:/var/tmp/portage/octave-2.1.69/image//usr/libexec/octave/2.1.69/exec: ls-R:/var/tmp/portage/octave-2.1.69/image//usr/libexec/octave/2.1.69/exec/i686-pc-linux-gnu: ls-R:/var/tmp/portage/octave-2.1.69/image//usr/libexec/octave/2.1.69/oct: ls-R:/var/tmp/portage/octave-2.1.69/image//usr/libexec/octave/2.1.69/oct/i686-pc-linux-gnu: ls-R:/var/tmp/portage/octave-2.1.69/image//usr/libexec/octave/2.1.69/site: ls-R:/var/tmp/portage/octave-2.1.69/image//usr/libexec/octave/2.1.69/site/exec: ls-R:/var/tmp/portage/octave-2.1.69/image//usr/libexec/octave/2.1.69/site/exec/i686-pc-linux-gnu: ls-R:/var/tmp/portage/octave-2.1.69/image//usr/libexec/octave/2.1.69/site/oct: ls-R:/var/tmp/portage/octave-2.1.69/image//usr/libexec/octave/2.1.69/site/oct/i686-pc-linux-gnu: ls-R:/var/tmp/portage/octave-2.1.69/image//usr/libexec/octave/site: ls-R:/var/tmp/portage/octave-2.1.69/image//usr/libexec/octave/site/exec: ls-R:/var/tmp/portage/octave-2.1.69/image//usr/libexec/octave/site/exec/i686-pc-linux-gnu: ls-R:/var/tmp/portage/octave-2.1.69/image//usr/libexec/octave/site/oct: ls-R:/var/tmp/portage/octave-2.1.69/image//usr/libexec/octave/site/oct/api-v13: ls-R:/var/tmp/portage/octave-2.1.69/image//usr/libexec/octave/site/oct/api-v13/i686-pc-linux-gnu: ls-R:/var/tmp/portage/octave-2.1.69/image//usr/libexec/octave/site/oct/i686-pc-linux-gnu:
bug still exist for sci-mathematics/octave-2.1.69
Created attachment 63616 [details, diff] octave_fix_ls-R.patch Here's a patch that should fix it.
Fixed in CVS for versions 2.69 and 2.71. Thanks for reporting, Patrizio. Thanks for the patch, Colin.