From: Andreas Oberritter <obi@opendreambox.org>
To: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] avahi-systemd: drop postrm, use prerm instead
Date: Mon, 21 May 2012 12:08:22 +0200 [thread overview]
Message-ID: <4FBA1416.3050102@opendreambox.org> (raw)
In-Reply-To: <lyliklevtz.fsf@ensc-virt.intern.sigma-chemnitz.de>
On 21.05.2012 11:18, Enrico Scholz wrote:
> Andreas Oberritter <obi@opendreambox.org> writes:
>
>>>> What's the use case for removing packages offline
>>>
>>> I am developing very much with NFS root filesystems (--> the temporary
>>> image directory which is kept by IMAGE_KEEPROOTFS=1). Packaging operations
>>> like install, remove or upgrade are common actions to test recipes and
>>> applications.
>>
>> Just to make sure we're talking about the same thing: Do you run
>> opkg-cl on the build machine to remove or upgrade packages inside the
>> target's NFS root?
>
> yes; I am working on the build machine. The NFS filesystem is mounted
> read-only on the target.
How do you handle prerm and postrm scripts that fail because $D is set?
How do you handle the majority of scripts that don't care about $D at
all? I think your use case is unsupported and always will be.
In contrast, packages having failing postinst scripts will re-run their
scripts on the target on first boot.
Regards,
Andreas
next prev parent reply other threads:[~2012-05-21 10:18 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
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 [this message]
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=4FBA1416.3050102@opendreambox.org \
--to=obi@opendreambox.org \
--cc=enrico.scholz@sigma-chemnitz.de \
--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 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.