All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: poky@yoctoproject.org
Subject: [PATCH 0/2] Preserve hard links
Date: Tue,  8 Feb 2011 23:51:44 -0600	[thread overview]
Message-ID: <cover.1297230569.git.mark.hatle@windriver.com> (raw)

While working on another part of the system, I noticed that Poky didn't appear
to be preserving any hard links in the system.  This change not only
preserves hardlinks during packaging, but also shrinks the overall
disk space required for a build.  In my poky-image-minimal my required
footprint shank by 200+ MB.

The second part of this patch I took a guess as to the right components to
modify.  It has passed the testing I've performed so far, but I'm not
100% sure that it's correct.  I believe a bit of additional review may be
necessary.

Pull URL: git://git.pokylinux.org/poky-contrib.git
  Branch: mhatle/hardlink
  Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=mhatle/hardlink

Thanks,
    Mark Hatle <mark.hatle@windriver.com>
---


Mark Hatle (2):
  package.bbclass: Preserve hard links!
  Misc hard link fixes

 meta/classes/libc-package.bbclass     |   12 ++++++------
 meta/classes/package.bbclass          |   18 +++++++++++++++++-
 meta/classes/populate_sdk_deb.bbclass |    2 +-
 meta/classes/sourcepkg.bbclass        |    2 +-
 meta/classes/staging.bbclass          |    2 +-
 5 files changed, 26 insertions(+), 10 deletions(-)

-- 
1.7.3.4



             reply	other threads:[~2011-02-09  5:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-09  5:51 Mark Hatle [this message]
2011-02-09  5:51 ` [PATCH 1/2] package.bbclass: Preserve hard links! Mark Hatle
2011-02-09  5:51 ` [PATCH 2/2] Misc hard link fixes Mark Hatle
2011-02-09 12:20 ` [PATCH 0/2] Preserve hard links Richard Purdie
2011-02-09 13:10   ` Richard Purdie

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=cover.1297230569.git.mark.hatle@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=poky@yoctoproject.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.