From: Mark Hatle <mark.hatle@windriver.com>
To: <poky@yoctoproject.org>
Subject: Re: [PATCH] rpm: Move postinsts to /var
Date: Wed, 4 Jan 2012 09:55:46 -0600 [thread overview]
Message-ID: <4F047682.5030204@windriver.com> (raw)
In-Reply-To: <1325643446.24646.11.camel@lenny>
On 1/3/12 8:17 PM, Colin Walters wrote:
> On Tue, 2012-01-03 at 16:54 -0800, Saul Wold wrote:
>> On 01/03/2012 10:48 AM, Colin Walters wrote:
>>> My OS has read-only bind mounts over most directories (including
>>> /etc), with the exception of /var. Since these scripts need to
>>> be run once and then deleted, it's better for me if these are in
>>> /var, and won't hurt anyone else for them to be there.
>>>
>>> You fixed this for RPM, does it exist for deb and ipkg also?
>
> From a glance, no:
>
> rootfs_deb.bbclass
> # Attempt to run postinsts
> # Mark packages with postinst failures as unpacked
> for i in ${IMAGE_ROOTFS}/var/lib/dpkg/info/*.postinst; do
> if [ -f $i ]&& ! sh $i configure; then
> _flag unpacked `basename $i .postinst`
> fi
> done
>
> rootfs_ipk.bbclass:
> for i in ${IMAGE_ROOTFS}${opkglibdir}/info/*.postinst; do
> if [ -f $i ]&& ! sh $i configure; then
> runtime_script_required=1
> opkg-cl ${IPKG_ARGS} flag unpacked `basename $i .postinst`
> fi
> done
Based on the above, I would then suggest you use /var/lib/rpm/info/*.postinst
That way the files are contained within the rpm directory of database and
associated files. Otherwise, I agree, this is a bug in the current
implementation. It shouldn't be using etc for things that can change.
--Mark
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
prev parent reply other threads:[~2012-01-04 15:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 18:48 [PATCH] rpm: Move postinsts to /var Colin Walters
2012-01-04 0:54 ` [poky] " Saul Wold
2012-01-04 0:54 ` Saul Wold
2012-01-04 2:17 ` Colin Walters
2012-01-04 15:55 ` Mark Hatle [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=4F047682.5030204@windriver.com \
--to=mark.hatle@windriver.com \
--cc=poky@yoctoproject.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.