Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 6/6] libsemanage: bump to version 2.5
Date: Fri, 24 Jun 2016 10:02:17 +0200	[thread overview]
Message-ID: <20160624100217.4d4d7f25@free-electrons.com> (raw)
In-Reply-To: <1466736201-17310-6-git-send-email-Aduskett@gmail.com>

Hello,

Thanks for your patch. See my comments below.

On Thu, 23 Jun 2016 22:43:21 -0400, Adam Duskett wrote:

>  .../libsemanage/0001-execption-lib-path-fix.patch  | 14 -------------

You are removing this patch, why?

> diff --git a/package/libsemanage/0001-workaround-blackfin-issue.patch b/package/libsemanage/0001-workaround-blackfin-issue.patch
> new file mode 100644
> index 0000000..6208ee7
> --- /dev/null
> +++ b/package/libsemanage/0001-workaround-blackfin-issue.patch
> @@ -0,0 +1,13 @@
> +diff --git a/src/dso.h b/src/dso.h
> +index 5c69aae..90ba3bf 100644

This patch got renamed, but in the process, you completely removed the
description of the patch and the Signed-off-by line. This is not good.


> diff --git a/package/libsemanage/Config.in b/package/libsemanage/Config.in
> index 5e9ad8f..cff4c07 100644
> --- a/package/libsemanage/Config.in
> +++ b/package/libsemanage/Config.in
> @@ -1,9 +1,9 @@
>  config BR2_PACKAGE_LIBSEMANAGE
>  	bool "libsemanage"
> -	select BR2_PACKAGE_LIBSELINUX
>  	select BR2_PACKAGE_USTR
>  	select BR2_PACKAGE_BZIP2
>  	depends on BR2_TOOLCHAIN_HAS_THREADS
> +	depends on BR2_PACKAGE_LIBSELINUX

Why are you changing from a depends on to a select ? The original
"select" is the correct thing to do.

>  	depends on !BR2_STATIC_LIBS
>  	depends on !BR2_TOOLCHAIN_USES_MUSL # getpwent_r()
>  	depends on !BR2_arc
> @@ -18,7 +18,7 @@ config BR2_PACKAGE_LIBSEMANAGE
>  
>  	  http://selinuxproject.org/page/Main_Page
>  
> -comment "libsemanage needs a toolchain w/ threads, dynamic library"
> +comment "libsemanage needs a toolchain w/ threads, dynamic library, libselinux"
>  	depends on !BR2_arc
>  	depends on !BR2_TOOLCHAIN_USES_MUSL
> -	depends on !BR2_TOOLCHAIN_HAS_THREADS || BR2_STATIC_LIBS
> +	depends on !BR2_TOOLCHAIN_HAS_THREADS || BR2_STATIC_LIBS || !BR2_PACKAGE_LIBSELINUX

As per my comment above, this change is not necessary.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-06-24  8:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-24  2:43 [Buildroot] [PATCH 1/1] Add libselinux and libsepol dependency for SELinux support Adam Duskett
2016-06-24  2:43 ` [Buildroot] [PATCH 2/6] Audit: bump to version 2.5.2 Adam Duskett
2016-06-24  2:43 ` [Buildroot] [PATCH 3/6] checkpolicy: bump to version 2.5 Adam Duskett
2016-06-24  2:43 ` [Buildroot] [PATCH 4/6] libsepol: " Adam Duskett
2016-06-24  7:36   ` Thomas Petazzoni
2016-06-24  2:43 ` [Buildroot] [PATCH 5/6] libselinux: " Adam Duskett
2016-06-24  7:38   ` Thomas Petazzoni
2016-06-24  2:43 ` [Buildroot] [PATCH 6/6] libsemanage: " Adam Duskett
2016-06-24  8:02   ` Thomas Petazzoni [this message]
2016-06-24  7:46 ` [Buildroot] [PATCH 1/1] Add libselinux and libsepol dependency for SELinux support Thomas Petazzoni

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=20160624100217.4d4d7f25@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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