Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Hongxu Jia <hongxu.jia@windriver.com>
To: Christopher Larson <clarson@kergoth.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] logrotate: do not move binary logrotate to /usr/bin
Date: Tue, 17 Nov 2015 09:35:59 +0800	[thread overview]
Message-ID: <564A847F.2050004@windriver.com> (raw)
In-Reply-To: <CABcZANmU7w-__Xp6cMb1PFcxRdsjoX-ZEQkwBe1uxYhu-LnbTA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2208 bytes --]

On 11/17/2015 12:32 AM, Christopher Larson wrote:
>
> On Mon, Nov 2, 2015 at 1:33 AM, Hongxu Jia <hongxu.jia@windriver.com 
> <mailto:hongxu.jia@windriver.com>> wrote:
>
>     In oe-core commit a46d3646a3e1781be4423b508ea63996b3cfca8a
>     ...
>     Author: Fahad Usman <fahad_usman@mentor.com
>     <mailto:fahad_usman@mentor.com>>
>     Date:   Tue Aug 26 13:16:48 2014 +0500
>
>     logrotate: obey our flags
>
>         Needed to quiet GNU_HASH warnings, and some minor fixes.
>     ...
>     it explicitly move logrotate to /usr/bin without any reason,
>     which is against the original Linux location /usr/sbin.
>
>     So partly revert the above commit which let logrotate be
>     kept in the original place /usr/sbin.
>
>     Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com
>     <mailto:hongxu.jia@windriver.com>>
>     ---
>      meta/recipes-extended/logrotate/logrotate_3.9.1.bb
>     <http://logrotate_3.9.1.bb> | 2 +-
>      1 file changed, 1 insertion(+), 1 deletion(-)
>
>     diff --git a/meta/recipes-extended/logrotate/logrotate_3.9.1.bb
>     <http://logrotate_3.9.1.bb>
>     b/meta/recipes-extended/logrotate/logrotate_3.9.1.bb
>     <http://logrotate_3.9.1.bb>
>     index 7d0a159..5f1a601 100644
>     --- a/meta/recipes-extended/logrotate/logrotate_3.9.1.bb
>     <http://logrotate_3.9.1.bb>
>     +++ b/meta/recipes-extended/logrotate/logrotate_3.9.1.bb
>     <http://logrotate_3.9.1.bb>
>     @@ -53,7 +53,7 @@ do_compile_prepend() {
>      }
>
>      do_install(){
>     -    oe_runmake install DESTDIR=${D} PREFIX=${D} MANDIR=${mandir}
>     BINDIR=${bindir}
>     +    oe_runmake install DESTDIR=${D} PREFIX=${D} MANDIR=${mandir}
>          mkdir -p ${D}${sysconfdir}/logrotate.d
>          mkdir -p ${D}${sysconfdir}/cron.daily
>          mkdir -p ${D}${localstatedir}/lib
>
>
> This just makes it not obey our target paths again, using its 
> hardcoded destination. Why not pass BINDIR=${sbindir} instead?

It is fine to me

//Hongxu


> -- 
> Christopher Larson
> clarson at kergoth dot com
> Founder - BitBake, OpenEmbedded, OpenZaurus
> Maintainer - Tslib
> Senior Software Engineer, Mentor Graphics


[-- Attachment #2: Type: text/html, Size: 5084 bytes --]

      reply	other threads:[~2015-11-17  1:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-02  8:33 [PATCH 0/1] logrotate: do not move binary logrotate to /usr/bin Hongxu Jia
2015-11-02  8:33 ` [PATCH 1/1] " Hongxu Jia
2015-11-16 16:32   ` Christopher Larson
2015-11-17  1:35     ` Hongxu Jia [this message]

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=564A847F.2050004@windriver.com \
    --to=hongxu.jia@windriver.com \
    --cc=clarson@kergoth.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox