this is just a demonstration.. and a real one: [85p] tigre : ~ $ emerge -u -e xine-ui -p These are the packages that I would merge, in order. Calculating dependencies !!! Couldn't find match for -e; aborting. [85p] tigre : ~ $ emerge -u --emptytree xine-ui -p These are the packages that I would merge, in order. Calculating dependencies ...done! [ebuild N ] media-libs/libdvdcss-0.0.3.3 to / [ebuild N ] media-libs/libdvdread-0.9.2 to / [ebuild N ] media-libs/win32codecs-0.60 to / [ebuild N ] sys-devel/gettext-0.11.1 to / [ebuild N ] media-libs/xine-lib-0.9.8-r1 to / [ebuild N ] sys-libs/zlib-1.1.4 to / [ebuild N ] media-libs/libpng-1.0.12 to / [ebuild N ] media-video/xine-ui-0.9.8-r2 to / [85p] tigre : ~ $ qpkg portage sys-apps/portage-1.4-r4 sys-apps/portage-1.8.11 * sys-apps/portage-1.8.8-r1 Since --emptytree and -e are suposed to have the same behaviour, i believe that this is a small bug in portage. P.S.: the bug tracking page is very confusing... can't we get anything simpler??
Geert: looks like I forgot to add support for the "-e" short option. Could you fix this for me?
Fixed in portage 1.8.13, you didn't forget it. My short option algo didn't handle 2 successive seperate short options well.