From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11046] New: Git package binaries are ~180MB (compared to ~20MB in stable branches).
Date: Thu, 24 May 2018 18:16:46 +0000 [thread overview]
Message-ID: <bug-11046-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=11046
Bug ID: 11046
Summary: Git package binaries are ~180MB (compared to ~20MB in
stable branches).
Product: buildroot
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: paulstewartis at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---
Created attachment 7601
--> https://bugs.busybox.net/attachment.cgi?id=7601&action=edit
Test config from Y Morin.
When I build a config with git enabled with 2018.05-rc2 the git binaries in
/usr/libexec/git-core are over 180MB. When I build the same config with
2018.02.2 (and all other stable versions I have used over the last few years)
the binaries are ~20MB or less.
Steps to reproduce:
1. Check out 2018.02.2 from git repo
2. Build the attached config.
3. Examine the git-core folder in the image tar file.
4. Check out 2018.05-rc2 from git repo
5. Build the attached config.
6. Examine the git-core folder in the image tar file.
My build system is openSUSE Leap 42.3 fully patched.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2018-05-24 18:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-24 18:16 bugzilla at busybox.net [this message]
2018-05-27 14:40 ` [Buildroot] [Bug 11046] Git package binaries are ~180MB (compared to ~20MB in stable branches) bugzilla at busybox.net
2018-05-27 17:37 ` bugzilla at busybox.net
2018-05-27 20:25 ` bugzilla at busybox.net
2018-05-27 20:51 ` bugzilla at busybox.net
2018-05-27 21:49 ` bugzilla at busybox.net
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=bug-11046-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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.