All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Ming Liu <liu.ming50@gmail.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>,
	Stefan Agner <stefan.agner@toradex.com>,
	simon.bueler@toradex.com
Subject: Re: [meta-oe] [PATCH] ostree: introduce OSTREE_PULL_TRANSPORT
Date: Sat, 7 Dec 2019 07:24:09 -0800	[thread overview]
Message-ID: <CAMKF1sphbUBWh3BTpoYcCyzH05dhm8yP+oOsh-wCdDAqXx7wpA@mail.gmail.com> (raw)
In-Reply-To: <1575723834-22763-1-git-send-email-liu.ming50@gmail.com>

On Sat, Dec 7, 2019 at 5:04 AM <liu.ming50@gmail.com> wrote:
>
> From: Ming Liu <liu.ming50@gmail.com>
>
> It could be soup or curl, for convenience to be overridden by other
> meta layers, like in meta-updater, it is choosing curl as the pull
> transport.
>
> Signed-off-by: Ming Liu <liu.ming50@gmail.com>
> ---
>  meta-oe/recipes-extended/ostree/ostree_2019.5.bb | 11 +++++++----
>  1 file changed, 7 insertions(+), 4 deletions(-)
>
> diff --git a/meta-oe/recipes-extended/ostree/ostree_2019.5.bb b/meta-oe/recipes-extended/ostree/ostree_2019.5.bb
> index 4f437f3..c3e3a12 100644
> --- a/meta-oe/recipes-extended/ostree/ostree_2019.5.bb
> +++ b/meta-oe/recipes-extended/ostree/ostree_2019.5.bb
> @@ -43,6 +43,11 @@ S = "${WORKDIR}/git"
>
>  inherit autotools bash-completion gobject-introspection gtk-doc manpages pkgconfig ptest-gnome systemd
>
> +# Value: soup or curl
> +# We include soup because ostree can't (currently) be built without
> +# soup or curl - https://github.com/ostreedev/ostree/issues/1897
> +OSTREE_PULL_TRANSPORT ??= "soup"

are these options exclusive? then we need a check as well to ensure
both are not used

> +
>  # Package configuration - match ostree defaults, but without rofiles-fuse
>  # otherwise we introduce a dependendency on meta-filesystems
>  #
> @@ -50,15 +55,13 @@ inherit autotools bash-completion gobject-introspection gtk-doc manpages pkgconf
>  PACKAGECONFIG ??= " \
>      ${@bb.utils.filter('DISTRO_FEATURES', 'selinux smack', d)} \
>      ${@bb.utils.contains('DISTRO_FEATURES', 'systemd', 'systemd libmount', '', d)} \
> -    soup \
> +    ${OSTREE_PULL_TRANSPORT} \
>  "
>
> -# We include soup because ostree can't (currently) be built without
> -# soup or curl - https://github.com/ostreedev/ostree/issues/1897
>  PACKAGECONFIG_class-native ??= " \
>      ${@bb.utils.filter('DISTRO_FEATURES', 'selinux smack', d)} \
>      builtin-grub2-mkconfig \
> -    soup \
> +    ${OSTREE_PULL_TRANSPORT} \
>  "
>
>  PACKAGECONFIG[avahi] = "--with-avahi, --without-avahi, avahi"
> --
> 2.7.4
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel


  reply	other threads:[~2019-12-07 15:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-07 13:03 [meta-oe] [PATCH] ostree: introduce OSTREE_PULL_TRANSPORT liu.ming50
2019-12-07 15:24 ` Khem Raj [this message]
2019-12-07 17:23   ` Alex Kiernan
2019-12-07 18:46     ` Khem Raj
2019-12-07 21:22       ` Ming Liu

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=CAMKF1sphbUBWh3BTpoYcCyzH05dhm8yP+oOsh-wCdDAqXx7wpA@mail.gmail.com \
    --to=raj.khem@gmail.com \
    --cc=liu.ming50@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=simon.bueler@toradex.com \
    --cc=stefan.agner@toradex.com \
    /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.