All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH][meta-oe] systemd: add postrm u-a calls
Date: Mon, 21 Nov 2011 10:33:05 +0100	[thread overview]
Message-ID: <jad5sh$iv7$1@dough.gmane.org> (raw)
In-Reply-To: <20111121084630.GD3565@jama.jama.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Op 21-11-11 09:46, Martin Jansa schreef:
> On Wed, Nov 16, 2011 at 03:15:17PM +0100, Martin Jansa wrote:
>> On Thu, Nov 10, 2011 at 09:22:12AM +0100, Anders Darander wrote:
>>> * Martin Jansa <martin.jansa@gmail.com> [111110 08:57]:
>>>> On Thu, Nov 10, 2011 at 08:44:49AM +0100, Anders Darander wrote:
>>>>> * Martin Jansa <martin.jansa@gmail.com> [111109 20:25]:
>>>>>> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> --- 
>>>>>> meta-oe/recipes-core/systemd/systemd_git.bb |   11 +++++++++-- 
>>>>>> 1 files changed, 9 insertions(+), 2 deletions(-)
>>> 
>>>>>> diff --git a/meta-oe/recipes-core/systemd/systemd_git.bb
>>>>>> b/meta-oe/recipes-core/systemd/systemd_git.bb index
>>>>>> 90862a3..d1d4306 100644 ---
>>>>>> a/meta-oe/recipes-core/systemd/systemd_git.bb +++
>>>>>> b/meta-oe/recipes-core/systemd/systemd_git.bb @@ -14,7 +14,7 @@
>>>>>> inherit gitpkgv # TODO: # u-a for runlevel and telinit -# u-a
>>>>>> prerm
>>> 
>>>>> Here on your todo list, it stated u-a for prerm, but you applied
>>>>> it to the postrm. In this case, it probably doesn't really
>>>>> matter, but I'd still guess that it would make more sense to
>>>>> remove the u-a before removing the binaries. Although, I don't
>>>>> think it'll actually cause any problems in this case.
>>> 
>>>> I did what u-a.bbclass usually do.. if you think it should be in
>>>> prerm then it would be best to first fix in u-a.bbclass and then we
>>>> can update the rest of metadata.
>>> 
>>> Yeah, like I said, is't likely not a real problem. There'll probably 
>>> just be a tiny window during which, in this case, e.g. reboot isn't 
>>> available, before u-a has been told to change the reboot link.
>>> 
>>> I'm currently just a little bit catious as I've recently stumbled
>>> upon post-/prerm issues using rpm... (Although the ones I know of
>>> (busybox updates, rsyslog removal) are either fixed or there has been
>>> patches submitted).
>> 
>> So should I change postrm to prerm in this patch or is there other 
>> reason why it wasn't applied yet?

I was waiting for Anders to comment on it :) Changing to prerm would be better.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAk7KGs8ACgkQMkyGM64RGpFddACghK4Srey32MmPC9KSCl5uLP4T
KDwAoKc4IGiGwRrOVXzgRtHTjmhxYzra
=QnvQ
-----END PGP SIGNATURE-----




  reply	other threads:[~2011-11-21  9:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-09 19:23 [PATCH][meta-oe] systemd: add postrm u-a calls Martin Jansa
2011-11-10  7:44 ` Anders Darander
2011-11-10  7:56   ` Martin Jansa
2011-11-10  8:22     ` Anders Darander
2011-11-16 14:15       ` Martin Jansa
2011-11-21  8:46         ` Martin Jansa
2011-11-21  9:33           ` Koen Kooi [this message]
2011-11-21  9:45             ` [meta-oe v2] systemd: add prerm " Martin Jansa
2011-11-21 11:06             ` [PATCH][meta-oe] systemd: add postrm " Anders Darander

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='jad5sh$iv7$1@dough.gmane.org' \
    --to=koen@dominion.thruhere.net \
    --cc=openembedded-devel@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.