From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Randy MacLeod <randy.macleod@windriver.com>,
deepesh.varatharajan@windriver.com
Cc: Shivaprasad.Moodalappa@windriver.com,
Sundeep.Kokkonda@windriver.com, Khem Raj <raj.khem@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH V4 2/3] rust: Upgrade 1.82.0->1.83.0 --> bloat alert !!
Date: Fri, 07 Mar 2025 23:37:41 +0000 [thread overview]
Message-ID: <5d748ede629df75d0ed30df5418b42b936d5416b.camel@linuxfoundation.org> (raw)
In-Reply-To: <c411d58d-bd27-4107-9b98-e39de14204df@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 889 bytes --]
On Fri, 2025-03-07 at 16:02 -0500, Randy MacLeod wrote:
>
> ❯ for i in `ls -d *src`; do du -sh $i; done
> 3.5G rustc-1.82.0-src
> 4.8G rustc-1.83.0-src
> 4.9G rustc-1.84.0-src
> 3.9G rustc-1.85.0-src
>
> I didn't check for the other 4 GB yet...
>
>
>
rust, rust-native, nativesdk-rust, cargo and so on.
> Should we do that an host the tarball on yoctoproject.org?
> Should we write a custom unpack rule to --exclude=rustc-1.83.0-
> src/src/gcc ?
Or just delete the directory in a do_unpack postfunc?
Or wait for 1.85?
This is annoying "bloat" which we at least need to identify and work
out a plan for.
>
>
> Next week, I'll also dig into the 'tmp' usage increase to understand
> where the 5 GB that Richard reported comes from.
See above, I'm guessing so it needs to be confirmed but...
Cheers,
Richard
>
[-- Attachment #2: Type: text/html, Size: 1954 bytes --]
next prev parent reply other threads:[~2025-03-07 23:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 13:44 [PATCH V4 1/3] rust: Fix build break because of download-ci-llvm Deepesh.Varatharajan
2025-03-05 13:44 ` [PATCH V4 2/3] rust: Upgrade 1.82.0->1.83.0 Deepesh.Varatharajan
2025-03-07 21:02 ` [OE-core] [PATCH V4 2/3] rust: Upgrade 1.82.0->1.83.0 --> bloat alert !! Randy MacLeod
2025-03-07 23:37 ` Richard Purdie [this message]
2025-03-13 18:48 ` Randy MacLeod
2025-03-14 12:32 ` Yash Shinde
2025-03-14 12:52 ` Yash Shinde
2025-03-14 13:48 ` Randy MacLeod
2025-03-14 15:50 ` Yash Shinde
2025-03-18 0:35 ` Randy MacLeod
2025-03-18 10:34 ` Yash Shinde
2025-03-12 9:52 ` [OE-core] [PATCH V4 2/3] rust: Upgrade 1.82.0->1.83.0 Alexander Kanavin
2025-03-14 4:38 ` Deepesh Varatharajan
2025-03-05 13:44 ` [PATCH V4 3/3] rust: Oe-selftest changes for rust v1.83.0 Deepesh.Varatharajan
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=5d748ede629df75d0ed30df5418b42b936d5416b.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Shivaprasad.Moodalappa@windriver.com \
--cc=Sundeep.Kokkonda@windriver.com \
--cc=deepesh.varatharajan@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=randy.macleod@windriver.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox