From: Philip Balister <philip@balister.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] packagegroup-core-sdk.bb: Drop distcc from the core-sdk.
Date: Tue, 16 Jun 2015 07:33:11 -0400 [thread overview]
Message-ID: <55800977.5070800@balister.org> (raw)
In-Reply-To: <1433189842-17654-1-git-send-email-philip@balister.org>
Ping
On 06/01/2015 04:17 PM, Philip Balister wrote:
> distcc has been used in the past to speed up native compile across
> several machines. This is less an issue on modern embedded systems.
>
> Also, improvements in sdk generation have reduced the need for on target
> compile of large projects.
>
> Since the distcc packages start a daemon at boot, drop it from the
> packagegroup to avoid having some slight runtime impact on systems
> installing an sdk.
>
> Signed-off-by: Philip Balister <philip@balister.org>
> ---
> meta/recipes-core/packagegroups/packagegroup-core-sdk.bb | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/meta/recipes-core/packagegroups/packagegroup-core-sdk.bb b/meta/recipes-core/packagegroups/packagegroup-core-sdk.bb
> index a41eada..9b26387 100644
> --- a/meta/recipes-core/packagegroups/packagegroup-core-sdk.bb
> +++ b/meta/recipes-core/packagegroups/packagegroup-core-sdk.bb
> @@ -23,7 +23,6 @@ RDEPENDS_packagegroup-core-sdk = "\
> findutils \
> quilt \
> less \
> - distcc \
> ldd \
> file \
> tcl"
>
prev parent reply other threads:[~2015-06-16 11:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 20:17 [PATCH 1/2] packagegroup-core-sdk.bb: Drop distcc from the core-sdk Philip Balister
2015-06-01 20:17 ` [PATCH 2/2] packagegroup-core-tools-profile.bb: Remove oprofile Philip Balister
2015-06-16 11:33 ` Philip Balister
2015-06-16 12:08 ` Burton, Ross
2015-06-16 12:33 ` Philip Balister
2015-06-16 12:35 ` Burton, Ross
2015-06-16 11:33 ` Philip Balister [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55800977.5070800@balister.org \
--to=philip@balister.org \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.