Disabling the bzip2 towards the end of emerge

asharif

unread,

Mar 20, 2012, 1:35:27 PM3/20/12

to Chromium OS dev

When emerging a package that installs a lot of files, I see this towards the end of the command:

* Removing /usr/lib*/*.la

* Removing /etc/init.d

* Removing /etc/conf.d

* Removing /etc/logrotate.d

And it gets stuck there for a while. top shows bzip2 is running.

I've tried running emerge with:

PORTAGE_COMPRESS="" emerge --buildpkg=n <package> and it still does the compression at the end. Is there a flag I could pass to emerge to disable the compression step towards the end? It would speed up my development incremental builds by a lot.

Brian Harring

unread,

Mar 20, 2012, 4:49:15 PM3/20/12

to asharif, Chromium OS dev

On Tue, Mar 20, 2012 at 10:35 AM, asharif <ash...@chromium.org> wrote:

When emerging a package that installs a lot of files, I see this towards the end of the command:

* Removing /usr/lib*/*.la
* Removing /etc/init.d
* Removing /etc/conf.d

* Removing /etc/logrotate.d

And it gets stuck there for a while. top shows bzip2 is running.

bzip2, or pbzip2?

I've tried running emerge with:

PORTAGE_COMPRESS="" emerge --buildpkg=n <package> and it still does the compression at the end. Is there a flag I could pass to emerge to disable the compression step towards the end? It would speed up my development incremental builds by a lot.

If you're seeing it with --buildpkg=n, then it's likely an ebuild itself doing the compression rather than portage; use `ps fuax` to pull the process tree (or pstree, thinking about it), and you'll likely see the parent is an autotest script.

~brian

Mandeep Singh Baines

unread,

Mar 20, 2012, 5:08:13 PM3/20/12

to asharif, Chromium OS dev

You need to do:

FEATURES=-buildpkg emerge ...

The --buildpkg=n is unnecessary.

> --
> Chromium OS Developers mailing list: chromiu...@chromium.org
> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en

Brian Harring

unread,

Mar 20, 2012, 5:26:10 PM3/20/12

to asharif, Mandeep Baines, Chromium OS dev

On Tue, Mar 20, 2012 at 2:08 PM, Mandeep Singh Baines <m...@chromium.org> wrote:

asharif (ash...@chromium.org) wrote:
> When emerging a package that installs a lot of files, I see this towards
> the end of the command:
>
> * Removing /usr/lib*/*.la
> * Removing /etc/init.d
> * Removing /etc/conf.d
> * Removing /etc/logrotate.d
>
> And it gets stuck there for a while. top shows bzip2 is running.
>
> I've tried running emerge with:
>
> PORTAGE_COMPRESS="" emerge --buildpkg=n <package> and it still does the
> compression at the end. Is there a flag I could pass to emerge to disable
> the compression step towards the end? It would speed up my development
> incremental builds by a lot.
>

You need to do:

FEATURES=-buildpkg emerge ...

The --buildpkg=n is unnecessary.

That option *should* suppress the feature. If disabling the feature globally fixes it (and you're positive it's not autotests packager), please open a ticket and file it my way.

Thanks-

~brian

Zac Medico

unread,

Mar 21, 2012, 3:22:36 AM3/21/12

to Brian Harring, asharif, Mandeep Baines, Chromium OS dev

On 03/20/2012 02:26 PM, Brian Harring wrote:
> On Tue, Mar 20, 2012 at 2:08 PM, Mandeep Singh Baines <m...@chromium.org

> You need to do:
>
> FEATURES=-buildpkg emerge ...
>
> The --buildpkg=n is unnecessary.
>
>
> That option *should* suppress the feature. If disabling the feature
> globally fixes it (and you're positive it's not autotests packager),
> please open a ticket and file it my way.

Here's a patch:

http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=500e0567432019835ef56e69d60266f9189c6700
--
Thanks,
Zac

Brian Harring

unread,

Mar 21, 2012, 4:19:45 AM3/21/12

to Zac Medico, asharif, Mandeep Baines, Chromium OS dev

@Zmedico:

Nice turn around time, thanks.

@msb/asharif:
I'll pull this into our portage w/in the week, and roll it out.
~brian

Reply all

Reply to author

Forward