From: Vladimir Zapolskiy <vz@mleia.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] package_ipk: allow to specify OPKG_ARGS in local.conf
Date: Thu, 03 Dec 2015 07:57:38 +0200 [thread overview]
Message-ID: <565FD9D2.3050707@mleia.com> (raw)
In-Reply-To: <CAJTo0Lbzvbwc34aXEMgfUJGnANMzaB+4ecM1=sa=8KONeTJukw@mail.gmail.com>
Hi Ross,
On 02.12.2015 11:48, Burton, Ross wrote:
>
> On 2 December 2015 at 04:48, Vladimir Zapolskiy <vz@mleia.com
> <mailto:vz@mleia.com>> wrote:
>
> sh: /tmp/opkg-5jPLag/run-postinsts-UsUtaI/preinst: /bin/sh: bad
> interpreter: Permission denied
>
>
> Whilst the patch is fine, this is worrying as noexec /tmp shouldn't
> break opkg. Maybe opkg should be changed to use something in /var for
> the scripts?
>
here IMHO two cases should be reviewed, build host side execution and
opkg on a target.
On a target /var/lib/opkg/$some_dir should be fine as a default
temporary directory, and it might be nice to have a config option in
/etc/opkg/opkg.conf
On a build host side /var/* may have permission restrictions also, so
* there should be a possibility to accept a user defined tmp dir,
* if /tmp is not good enough as a default opkg directory, probably some
subfolder of ${TOPDIR} should fit, either a fixed one or dynamic
somewhere in a working folder of bb recipe, which calls opkg.
Just my two cents.
With best wishes,
Vladimir
next prev parent reply other threads:[~2015-12-03 5:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 4:48 [PATCH] package_ipk: allow to specify OPKG_ARGS in local.conf Vladimir Zapolskiy
2015-12-02 9:48 ` Burton, Ross
2015-12-02 23:16 ` Alejandro del Castillo
2015-12-02 23:19 ` Burton, Ross
2015-12-03 1:03 ` Alejandro del Castillo
2015-12-03 5:57 ` Vladimir Zapolskiy [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-12-02 4:41 Vladimir Zapolskiy
2015-12-02 4:50 ` Vladimir Zapolskiy
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=565FD9D2.3050707@mleia.com \
--to=vz@mleia.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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.