Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Andreas Oberritter <obi@opendreambox.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] avahi-systemd: drop postrm, use prerm instead
Date: Wed, 16 May 2012 20:38:44 +0200	[thread overview]
Message-ID: <4FB3F434.2040703@opendreambox.org> (raw)
In-Reply-To: <89109968-DC24-477E-9E9D-2F255D1EB93B@dominion.thruhere.net>

On 16.05.2012 19:17, Koen Kooi wrote:
> 
> Op 16 mei 2012, om 18:55 heeft Andreas Oberritter het volgende geschreven:
> 
>> * Calling "systemctl disable" from postrm is too late and
>>  causes the following error:
>>
>> | Failed to issue method call: No such file or directory
>>
>> * Fix indentation of prerm for resulting shell snippet.
>> * Messing with $D is not needed in *rm scripts.
> 
> It very much is, you can offline remove scripts just like you can install them.

What's the use case for removing packages offline and where in OE is
this used? Is the majority of prerm- and postrm-scripts prepared for that?

Regards,
Andreas



  reply	other threads:[~2012-05-16 18:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-16 16:55 [PATCH] avahi-systemd: drop postrm, use prerm instead Andreas Oberritter
2012-05-16 17:17 ` Koen Kooi
2012-05-16 18:38   ` Andreas Oberritter [this message]
2012-05-16 18:50     ` Koen Kooi
2012-05-16 19:03       ` Andreas Oberritter
2012-05-18 15:06     ` Enrico Scholz
2012-05-21  8:46       ` Andreas Oberritter
2012-05-21  9:18         ` Enrico Scholz
2012-05-21 10:08           ` Andreas Oberritter
2012-05-21 11:04             ` Enrico Scholz
2012-05-21 11:49               ` Andreas Oberritter
2012-05-21 12:06                 ` Koen Kooi
2012-05-21 12:13                   ` Enrico Scholz
2012-05-21 12:20                     ` Koen Kooi
2012-05-21 12:33                       ` Enrico Scholz

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=4FB3F434.2040703@opendreambox.org \
    --to=obi@opendreambox.org \
    --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