On Wednesday, February 05, 2014 20:57:24 Arfrever wrote:
> Calling portageq multiple times would be too slow for some tools.
i think this is the fundamental point you're trying to side step/ignore.
we've done work in the past to mitigate this. e.g. `portageq envvar -v`
allows you to list multi
2014-02-05 09:08 Mike Frysinger napisał(a):
> On Saturday, February 01, 2014 21:08:11 Arfrever Frehtes Taifersar Arahesis
> wrote:
> > bin/isolated-functions.sh contains at least 1 useful function, which could
> > be exposed for external consumers (without __ prefix), but must have
> > private nam
On Saturday, February 01, 2014 21:08:11 Arfrever Frehtes Taifersar Arahesis
wrote:
> 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 u
On Sat, Feb 1, 2014 at 12:08 PM, Arfrever Frehtes Taifersar Arahesis <
arfrever@gmail.com> wrote:
> 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/isola
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-fu
