Openembedded Core Discussions
 help / color / mirror / Atom feed
From: ChenQi <Qi.Chen@windriver.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: qingtao.cao@windriver.com,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH V2 1/9] busybox: remove the postinst part of the recipe
Date: Tue, 18 Jun 2013 09:37:24 +0800	[thread overview]
Message-ID: <51BFB9D4.8080606@windriver.com> (raw)
In-Reply-To: <CAP9ODKrhOpbGDXmU0Qhec5GJvzr1FFVv8TXdtT=AMJiOk-A2Rg@mail.gmail.com>

On 06/18/2013 01:52 AM, Otavio Salvador wrote:
> On Mon, Jun 17, 2013 at 2:49 AM,  <Qi.Chen@windriver.com> wrote:
>> From: Chen Qi <Qi.Chen@windriver.com>
>>
>> Remove the pkg_postinst_${PN} from this recipe, as it's redundant.
>> It basically wants to do the same thing as the update-alternatives
>> does. But it doesn't do it well.
>>
>> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
> Most of patch 1 and 2 should be merged; here you should drop the
> postinst and convert these to the update-alternative way so we don't
> have the tree broken after this patch and allow for bisect  to be
> used.
Hi Otavio,

Maybe there's some misunderstanding here.
To be clear, patch 1 and patch 2 do two different things.
Patch 1 removes postinst, it has nothing to do with patch 2, which fix 
busybox.inc to support the FEATURE_INDIVIDUAL.
And after this patch (patch 1), the tree is not broken. The busybox 
still works as it has been working so far.

[
And I just did a simple test to confirm this. On the lastest master, I 
removed the postinst part of busybox.inc, and built a 
core-image-minimal, it worked out well. Here's some output.
root@qemuarm:~# ls -l /bin/ | grep busybox
lrwxrwxrwx    1 root     root            12 Jun 18 01:31 ash -> /bin/busybox
-rwsr-xr-x    1 root     root        556824 Jun 18 01:27 busybox
lrwxrwxrwx    1 root     root            12 Jun 18 01:31 cat -> /bin/busybox
lrwxrwxrwx    1 root     root            12 Jun 18 01:31 chattr -> 
/bin/busybox
lrwxrwxrwx    1 root     root            12 Jun 18 01:31 chgrp -> 
/bin/busybox
lrwxrwxrwx    1 root     root            12 Jun 18 01:31 chmod -> 
/bin/busybox
lrwxrwxrwx    1 root     root            12 Jun 18 01:31 chown -> 
/bin/busybox
lrwxrwxrwx    1 root     root            12 Jun 18 01:31 cp -> /bin/busybox
....
]

Best Regards,
Chen Qi

> --
> Otavio Salvador                             O.S. Systems
> http://www.ossystems.com.br        http://projetos.ossystems.com.br
> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
>
>



  reply	other threads:[~2013-06-18  1:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-17  5:49 [PATCH V2 0/9] busybox miscellaneous fixes Qi.Chen
2013-06-17  5:49 ` [PATCH V2 1/9] busybox: remove the postinst part of the recipe Qi.Chen
2013-06-17 17:52   ` Otavio Salvador
2013-06-18  1:37     ` ChenQi [this message]
2013-06-18 12:06       ` Otavio Salvador
2013-06-17  5:49 ` [PATCH V2 2/9] busybox: add support for CONFIG_FEATURE_INDIVIDUAL Qi.Chen
2013-06-17  5:49 ` [PATCH V2 3/9] busybox: add a config fragment to enable login utilities Qi.Chen
2013-06-17  5:49 ` [PATCH V2 4/9] busybox: enable to list suid and non-suid app configs Qi.Chen
2013-06-17  5:49 ` [PATCH V2 5/9] busybox: add the ability to split the busybox binary Qi.Chen
2013-06-17  5:49 ` [PATCH V2 6/9] packagegroup-core-boot: use busybox as the default login manager Qi.Chen
2013-06-17  5:49 ` [PATCH V2 7/9] packagegroup-core-basic: set " Qi.Chen
2013-06-17  5:49 ` [PATCH V2 8/9] mingetty: lower the ALTERNATIVE_PRIORITY Qi.Chen
2013-06-17  5:49 ` [PATCH V2 9/9] tinylogin: remove recipe Qi.Chen
2013-06-17 10:17   ` Phil Blundell
2013-06-17 10:28     ` Richard Purdie
2013-06-17 10:59       ` Phil Blundell
2013-06-17 11:06         ` Richard Purdie
2013-06-17 11:15           ` Phil Blundell

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=51BFB9D4.8080606@windriver.com \
    --to=qi.chen@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    --cc=qingtao.cao@windriver.com \
    /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