bin/isolated-functions.sh contains at least 1 useful function, which could be exposed for external consumers
(without __ prefix), but must have private name (with __ prefix) when bin/isolated-functions.sh is used in
ebuild environment.

Possible solutions:
1. Make /usr/lib/portage/bin/isolated-functions.sh magically define non-private variants of useful functions
   when run in non-ebuild environment.
2. Provide /usr/bin/portage.bash, which would source isolated-functions.sh (and maybe other files) and define
   non-private variants of useful functions. /usr/bin/portage.bash would be easier sourceable due to PATH.
3. Provide /usr/lib/portage.bash, which would source isolated-functions.sh (and maybe other files) and define
   non-private variants of useful functions.
4. Another location...

(I would probably prefer solution #2.)

--
Arfrever Frehtes Taifersar Arahesis