All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Ohly <patrick.ohly@intel.com>
To: "André Draszik" <git@andred.net>, yocto@yoctoproject.org
Subject: Re: [meta-swupd][PATCH] layer.conf: exclude libarchive (bsdtar) dependency from swupd-client
Date: Thu, 16 Nov 2017 14:32:54 +0100	[thread overview]
Message-ID: <1510839174.5979.32.camel@intel.com> (raw)
In-Reply-To: <20171116100258.21588-1-git@andred.net>

On Thu, 2017-11-16 at 10:02 +0000, André Draszik wrote:
> From: André Draszik <adraszik@tycoint.com>
> 
> The swupd-client doesn't need to be rebuilt if libarchive
> changes, because swupd-client just invokes the command line
> utility bsdtar from the libarchive recipe, it doesn't link
> against libarchive.
> The bsdtar binary changing doesn't matter, as bsdtar's ABI
> (command line argument handling) wouldn't be changing.

This is about to change: 
https://github.com/clearlinux/swupd-client/issues/285 is being workedon, see 
https://github.com/clearlinux/swupd-client/pull/327

> Signed-off-by: André Draszik <adraszik@tycoint.com>
> ---
>  conf/layer.conf | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/conf/layer.conf b/conf/layer.conf
> index 50e7558..3af6992 100644
> --- a/conf/layer.conf
> +++ b/conf/layer.conf
> @@ -14,4 +14,5 @@ LAYERVERSION_meta-swupd = "1"
>  SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS += "\
>    oe-swupd-helpers->bash \
>    oe-swupd-helpers->busybox \
> +  swupd-client->libarchive \
>  "

For now this change is okay.

I just have one general problem: I'm not sure whether I should consider
myself the maintainer who merges this. I know that I am listed as
"tentative" maintainer, but it practice it hasn't been my job and I
don't have time for it in my spare time either.

I did some work with swupd again recently, resulting in https://github.
com/pohly/meta-swupd/commits/master and https://github.com/intel/intel-
iot-refkit/pull/318, but that's just a temporary activity.

I understand that this isn't a tenable situation for those of you using
meta-swupd; hopefully by the end of the year at the latest it'll be
resolved.

-- 
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.




      parent reply	other threads:[~2017-11-16 13:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-16 10:02 [meta-swupd][PATCH] layer.conf: exclude libarchive (bsdtar) dependency from swupd-client André Draszik
2017-11-16 10:04 ` André Draszik
2017-11-16 13:32 ` 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=1510839174.5979.32.camel@intel.com \
    --to=patrick.ohly@intel.com \
    --cc=git@andred.net \
    --cc=yocto@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.