All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Alejandro del Castillo <alejandro.delcastillo@ni.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] libsolv: add new recipe
Date: Thu, 10 Dec 2015 11:04:26 +1300	[thread overview]
Message-ID: <1750958.3rdPrcUnoM@peggleto-mobl.ger.corp.intel.com> (raw)
In-Reply-To: <1449694203-15173-1-git-send-email-alejandro.delcastillo@ni.com>

Hi Alejandro,

On Wed, 09 Dec 2015 14:50:03 Alejandro del Castillo wrote:
> Signed-off-by: Alejandro del Castillo <alejandro.delcastillo@ni.com>

So perhaps it was discussed elsewhere, but in any case if you want this to be 
added to OE-Core there needs to be something mentioned in the commit message 
about why - what needs this? If nothing, is OE-Core the best place for it?

> ---
>  meta/recipes-extended/libsolv/libsolv_0.6.14.bb | 26
> +++++++++++++++++++++++++ 1 file changed, 26 insertions(+)
>  create mode 100644 meta/recipes-extended/libsolv/libsolv_0.6.14.bb
> 
> diff --git a/meta/recipes-extended/libsolv/libsolv_0.6.14.bb
> b/meta/recipes-extended/libsolv/libsolv_0.6.14.bb new file mode 100644
> index 0000000..14955da
> --- /dev/null
> +++ b/meta/recipes-extended/libsolv/libsolv_0.6.14.bb
> @@ -0,0 +1,26 @@
> +SUMMARY = "Library for solving packages and reading repositories"
> +HOMEPAGE = "https://github.com/openSUSE/libsolv"
> +BUGTRACKER = "https://github.com/openSUSE/libsolv/issues"
> +SECTION = "devel"
> +LICENSE = "BSD"

LICENSE should be more specific - BSD-2-Clause, BSD-3-Clause, etc.

> +LIC_FILES_CHKSUM =
> "file://LICENSE.BSD;md5=62272bd11c97396d4aaf1c41bc11f7d8" +
>
> +SRC_URI = "https://github.com/openSUSE/libsolv/archive/0.6.14.zip"

Please use ${PV} instead of 0.6.14 here to make future upgrades easier.

> +SRC_URI[md5sum] = "171da68f08f672cacd1930643f8d1b4d"
> +SRC_URI[sha256sum] =
> "0263b11372012be9c83f1c01f7d55ea9464dde58c109f5ae4de1e52870034a45" 
> +
> +PACKAGES =+ "${PN}-tools ${PN}ext ${PN}ext-dbg"

The PACKAGES line should move down before the FILES lines since this has to do 
with packaging.

> +
> +S = "${WORKDIR}/libsolv-0.6.14"

As per SRC_URI, please use ${PV} instead of 0.6.14 here.

> +
> +inherit cmake
> +
> +EXTRA_OECMAKE = "-DLIB=${baselib}"
> +
> +DEPENDS = "expat zlib"
> +
> +FILES_${PN}-dev += "${datadir}/cmake/Modules/FindLibSolv.cmake"
> +FILES_${PN}-tools = "${bindir}/*"
> +FILES_${PN}ext = "${libdir}/${PN}ext.so.*"
> +FILES_${PN}ext-dbg = "${libdir}/.debug/${PN}ext.so.*"

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  reply	other threads:[~2015-12-09 22:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09 20:50 [PATCH] libsolv: add new recipe Alejandro del Castillo
2015-12-09 22:04 ` Paul Eggleton [this message]
2015-12-09 23:01   ` [PATCH v2] " Alejandro del Castillo
2015-12-10 21:22     ` [PATCH v3] " Alejandro del Castillo
2015-12-10 23:16       ` Andre McCurdy
2015-12-10 23:55         ` Burton, Ross
2015-12-11  0:15           ` Martin Jansa
2015-12-11  8:48             ` Burton, Ross
2015-12-11 21:29         ` [PATCH v4] " Alejandro del Castillo
2015-12-11 21:32           ` Martin Jansa
2015-12-12  0:14             ` [PATCH v5] " Alejandro del Castillo
2015-12-10  1:40   ` [PATCH] " Alejandro del Castillo

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=1750958.3rdPrcUnoM@peggleto-mobl.ger.corp.intel.com \
    --to=paul.eggleton@linux.intel.com \
    --cc=alejandro.delcastillo@ni.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 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.