[gentoo-portage-dev] emerging binary pkgs very slow on ppc32

We got an embedded target which we upded with binary pks(157 in this case) using: PKGDIR=/opt/fs/osappl04a-r30b-1/usr/portage/packages emerge --rebuilt-binaries --verbose --usepkgonly -NDu @world @cusfpv3 and this takes forever, about 1 hour not sure where to start looking for a cause, is this

Re: [gentoo-portage-dev] [PATCH] filter-bash-environment.py: use buffered input, raw bytes (bug 647654)

On Wed, Feb 14, 2018 at 3:38 PM, Zac Medico wrote: > Use sys.stdin.buffer instead of sys.stdin.buffer.raw, for buffered input. > Also use raw bytes instead of unicode strings, in order to avoid making > assumptions about character encodings, and also to avoid overhead from >

Re: [gentoo-portage-dev] emerging binary pkgs very slow on ppc32

On 02/14/2018 07:49 AM, Joakim Tjernlund wrote: > We got an embedded target which we upded with binary pks(157 in this case) > using: > PKGDIR=/opt/fs/osappl04a-r30b-1/usr/portage/packages emerge > --rebuilt-binaries --verbose --usepkgonly -NDu @world @cusfpv3 > and this takes forever, about 1

[gentoo-portage-dev] [PATCH] filter-bash-environment.py: use buffered input, raw bytes (bug 647654)

Use sys.stdin.buffer instead of sys.stdin.buffer.raw, for buffered input. Also use raw bytes instead of unicode strings, in order to avoid making assumptions about character encodings, and also to avoid overhead from unicode decoding/encoding. Bug: https://bugs.gentoo.org/647654 ---

Re: [gentoo-portage-dev] [PATCH] filter-bash-environment.py: use buffered input, raw bytes (bug 647654)

On 02/14/2018 12:46 PM, Alec Warner wrote: > On Wed, Feb 14, 2018 at 3:38 PM, Zac Medico > wrote: > > Use sys.stdin.buffer instead of sys.stdin.buffer.raw, for buffered > input. > Also use raw bytes instead of unicode strings, in order

[gentoo-portage-dev] [PATCH v2] filter-bash-environment.py: use buffered input, raw bytes (bug 647654)

Use sys.stdin.buffer instead of sys.stdin.buffer.raw, for buffered input. Also use raw bytes instead of unicode strings, in order to avoid making assumptions about character encodings, and also to avoid overhead from unicode decoding/encoding. Since the % operator does not support bytes operands