public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Pascal Ouyang <xin.ouyang@windriver.com>
To: Xin Ouyang <Xin.Ouyang@windriver.com>
Cc: openembedded-core@www.linuxtogo.org,
	openembedded-core@lists.openembedded.org
Subject: Re: [V2 PATCH] libcgroup: fix the QA issue for pam_cgroup.so*
Date: Sat, 26 Jan 2013 17:13:43 +0800	[thread overview]
Message-ID: <51039E47.8090701@windriver.com> (raw)
In-Reply-To: <1359026733-1392-1-git-send-email-Xin.Ouyang@windriver.com>

于 2013年01月24日 19:25, Xin Ouyang 写道:
> PAM modules in ${base_libdir}/security/ should be binary .so files,
> not symlinks, so fix this. Since pam_cgroup.so is installed into
> ${base_libdir}/security, move libcgroup.so.* to ${base_libdir} to
> avoid "unsafe-references-in-binaries" QA issue.
>
> Signed-off-by: Xin Ouyang <Xin.Ouyang@windriver.com>
> ---
>   meta/recipes-core/libcgroup/libcgroup_0.37.1.bb |   15 +++++++++++++--
>   1 file changed, 13 insertions(+), 2 deletions(-)
>
> diff --git a/meta/recipes-core/libcgroup/libcgroup_0.37.1.bb b/meta/recipes-core/libcgroup/libcgroup_0.37.1.bb
> index e74f831..d217f7b 100644
> --- a/meta/recipes-core/libcgroup/libcgroup_0.37.1.bb
> +++ b/meta/recipes-core/libcgroup/libcgroup_0.37.1.bb
> @@ -23,5 +23,16 @@ FILES_cgroups-pam-plugin = "${base_libdir}/security/pam_cgroup.so*"
>   FILES_${PN}-dbg += "${base_libdir}/security/.debug"
>   FILES_${PN}-dev += "${base_libdir}/security/*.la"
>
> -# We really need the symlink so :(
> -INSANE_SKIP_cgroups-pam-plugin = "dev-so"
> +do_install_append() {
> +	# Moving libcgroup to base_libdir
> +	if [ ! ${D}${libdir} -ef ${D}${base_libdir} ]; then
> +		mkdir -p ${D}/${base_libdir}/
> +		mv -f ${D}${libdir}/libcgroup.so.* ${D}${base_libdir}/
> +		ln -sf ${D}${base_libdir}/libcgroup.so.1 ${D}${libdir}/libcgroup.so

I should not use absolute path for this symlink here.

rel_lib_prefix=`echo ${libdir} | sed 's,\(^/\|\)[^/][^/]*,..,g'`
ln -sf ${rel_lib_prefix}${base_libdir}/libcgroup.so.1 \
        ${D}${libdir}/libcgroup.so

V3 will be sent. Thanks.

- Pascal

> +	fi
> +	# pam modules in ${base_libdir}/security/ should be binary .so files, not symlinks.
> +	if [ -f ${D}${base_libdir}/security/pam_cgroup.so.0.0.0 ]; then
> +		mv -f ${D}${base_libdir}/security/pam_cgroup.so.0.0.0 ${D}${base_libdir}/security/pam_cgroup.so
> +		rm -f ${D}${base_libdir}/security/pam_cgroup.so.*
> +	fi
> +}
>





  parent reply	other threads:[~2013-01-26  9:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-24 11:25 [V2 PATCH] libcgroup: fix the QA issue for pam_cgroup.so* Xin Ouyang
2013-01-24 11:32 ` Burton, Ross
2013-01-26  9:13 ` Pascal Ouyang [this message]
2013-01-26 10:33   ` lei yang
2013-01-28  1:43     ` Pascal Ouyang

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=51039E47.8090701@windriver.com \
    --to=xin.ouyang@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-core@www.linuxtogo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox