All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Jan Siegmund <jan.siegmund0@hm.edu>,
	openembedded-core@lists.openembedded.org
Cc: Jan Siegmund <jsiegmund@arri.de>
Subject: Re: [PATCH v2] apt-native: Add libapt-pkg headers
Date: Sun, 04 Feb 2018 09:59:50 +0000	[thread overview]
Message-ID: <1517738390.3090.76.camel@linuxfoundation.org> (raw)
In-Reply-To: <20180203103314.2646-1-jsiegmun@hm.edu>

On Sat, 2018-02-03 at 11:33 +0100, Jan Siegmund wrote:
> From: Jan Siegmund <jsiegmund@arri.de>
> 
> Native tools were not able to use the headers of apt-pkg. This patch
> adds the feature.
> The headers were added from apt-pkg and apt-inst to the native
> recipe.
> The shipped headers match the ones in the Ubuntu package libapt-pkg-
> dev.
> 
> Signed-off-by: Jan Siegmund <jsiegmund@arri.de>
> ---
>  meta/recipes-devtools/apt/apt-native.inc | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/meta/recipes-devtools/apt/apt-native.inc b/meta/recipes-
> devtools/apt/apt-native.inc
> index 68f1b3ce2c..d82ffcc59f 100644
> --- a/meta/recipes-devtools/apt/apt-native.inc
> +++ b/meta/recipes-devtools/apt/apt-native.inc
> @@ -35,6 +35,8 @@ python do_install_config () {
>          outfile.close()
>  }
>  
> +FILES_${PN} += "${includedir}"
> +
>  do_install_base () {
>  	install -d ${D}${bindir}
>  	install -m 0755 bin/apt-cdrom ${D}${bindir}/

I suspect a native recipe doesn't need to set FILES?

Cheers,

Richard


  reply	other threads:[~2018-02-04 10:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-03 10:33 [PATCH v2] apt-native: Add libapt-pkg headers Jan Siegmund
2018-02-04  9:59 ` Richard Purdie [this message]
2018-02-04 11:05   ` Jan Siegmund

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=1517738390.3090.76.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=jan.siegmund0@hm.edu \
    --cc=jsiegmund@arri.de \
    --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 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.