Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Patrick Ohly <patrick.ohly@intel.com>
To: openembedded-core@lists.openembedded.org
Cc: Alexander Kanavin <alexander.kanavin@intel.com>
Subject: Re: [PATCH] libarchive: enable non-recursive extract/list
Date: Mon, 05 Dec 2016 08:26:12 +0100	[thread overview]
Message-ID: <1480922772.17535.24.camel@intel.com> (raw)
In-Reply-To: <1480585246-3278-1-git-send-email-patrick.ohly@intel.com>

On Thu, 2016-12-01 at 10:40 +0100, Patrick Ohly wrote:
> Required for meta-swupd performance enhancements: in meta-swupd, the
> so called "mega" image contains a rootfs with all files that can
> potentially be installed on a device. Other virtual image recipes need
> a subset of those files or directories, and a partial extraction from
> a single tar archive is faster than letting all virtual image recipes
> share access to a directory under a single pseudo instance.
> 
> It may be necessary to extract a directory with all of its attributes
> without the content of the directory, hence this patch. Upstream
> agreed to consider merging such a patch (see
> https://groups.google.com/forum/#!topic/libarchive-discuss/JO3hqSaAVfs)
> but has been slow in actually commenting on it, so for now it has
> to be carried as distro patch.

Ping?

Alexander, you touched libarchive most recently. Any thoughts on this?

I could carry the patch also in meta-swupd, if that's preferred. It just
doesn't feel very clean for such a layer to modify a core recipe like
that.

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.





      reply	other threads:[~2016-12-05  7:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-01  9:40 [PATCH] libarchive: enable non-recursive extract/list Patrick Ohly
2016-12-05  7:26 ` Patrick Ohly [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=1480922772.17535.24.camel@intel.com \
    --to=patrick.ohly@intel.com \
    --cc=alexander.kanavin@intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox