From: Saul Wold <sgw@linux.intel.com>
To: Colin Walters <walters@verbum.org>
Cc: poky <poky@yoctoproject.org>
Subject: Re: [poky] [PATCH] rpm: Move postinsts to /var
Date: Tue, 03 Jan 2012 16:54:57 -0800 [thread overview]
Message-ID: <4F03A361.3000408@linux.intel.com> (raw)
In-Reply-To: <1325616533.23339.10.camel@lenny>
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?
Sau!
>
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
WARNING: multiple messages have this Message-ID (diff)
From: Saul Wold <sgw@linux.intel.com>
To: Colin Walters <walters@verbum.org>
Cc: poky <poky@yoctoproject.org>
Subject: Re: [PATCH] rpm: Move postinsts to /var
Date: Tue, 03 Jan 2012 16:54:57 -0800 [thread overview]
Message-ID: <4F03A361.3000408@linux.intel.com> (raw)
In-Reply-To: <1325616533.23339.10.camel@lenny>
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?
Sau!
>
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
next prev parent reply other threads:[~2012-01-04 1:02 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 ` Saul Wold [this message]
2012-01-04 0:54 ` Saul Wold
2012-01-04 2:17 ` Colin Walters
2012-01-04 15:55 ` Mark Hatle
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=4F03A361.3000408@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=poky@yoctoproject.org \
--cc=walters@verbum.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.