From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/3] gpsd: cleanup udev rule permissions
Date: Thu, 5 Nov 2015 22:37:23 +0100 [thread overview]
Message-ID: <20151105223723.35e5069e@free-electrons.com> (raw)
In-Reply-To: <1446748914-12628-2-git-send-email-james.knight@rockwellcollins.com>
Dear James Knight,
On Thu, 5 Nov 2015 13:41:53 -0500, James Knight wrote:
> Adjust a generated udev rule file (25-gpsd.rules) to have user write
> permissions. This is to prevent rebuild issues when the gpsd package
> fails to re-install on a target (since the `cp` of the rule file will
> fail due to permissions).
>
> Signed-off-by: James Knight <james.knight@rockwellcollins.com>
> ---
> Changes v1 -> v2:
> - Package change introduced in change set 2.
> ---
> package/gpsd/gpsd.mk | 4 ++++
> 1 file changed, 4 insertions(+)
Applied after doing some minor tweaks to the commit title and the
comment in the code.
Could you report this issue to upstream gpsd? It is not normal IMO that
a projects doesn't support "make install; make install".
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-11-05 21:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 18:41 [Buildroot] [PATCH v2 1/3] gpsd: correct explicit nmea 0183 support flag James Knight
2015-11-05 18:41 ` [Buildroot] [PATCH v2 2/3] gpsd: cleanup udev rule permissions James Knight
2015-11-05 21:37 ` Thomas Petazzoni [this message]
2015-11-05 18:41 ` [Buildroot] [PATCH v2 3/3] gpsd: disable attempt to reload systemd James Knight
2015-11-05 21:39 ` Thomas Petazzoni
2015-11-06 16:07 ` James Knight
2015-11-05 21:00 ` [Buildroot] [PATCH v2 1/3] gpsd: correct explicit nmea 0183 support flag Thomas Petazzoni
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=20151105223723.35e5069e@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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