All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11046] Git package binaries are ~180MB (compared to ~20MB in stable branches).
Date: Sun, 27 May 2018 17:37:30 +0000	[thread overview]
Message-ID: <bug-11046-163-eSUtbOfM3D@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11046-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=11046

--- Comment #2 from Paul Stewart <paulstewartis@gmail.com> ---
(In reply to Arnout Vandecappelle from comment #1)

The post scripts only run if they are called out in the config, right?  Either
way, none of my scripts do anything with git.  I can definitely reproduce with
the attached, minimal, config.

The binaries are normal in target/usr/libexec/git-core. So I think you're on
the right track.

What's the best way for me to determine: "if the copies are made during the
install of git itself, or during the target-finalize step, or maybe even during
rootfs generation"?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2018-05-27 17:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-24 18:16 [Buildroot] [Bug 11046] New: Git package binaries are ~180MB (compared to ~20MB in stable branches) bugzilla at busybox.net
2018-05-27 14:40 ` [Buildroot] [Bug 11046] " bugzilla at busybox.net
2018-05-27 17:37 ` bugzilla at busybox.net [this message]
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-eSUtbOfM3D@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.