From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] aiccu: new package
Date: Thu, 5 Sep 2013 10:13:59 +0200 [thread overview]
Message-ID: <20130905101359.3be9c385@skate> (raw)
In-Reply-To: <028035D9-F009-4D2C-B63E-6D6BFD08D5B7@layer-7.net>
Dear Michael Rommel,
On Wed, 4 Sep 2013 22:50:42 +0200, Michael Rommel wrote:
> Regarding the installation there are three versions on the table:
>
> 1. Using the recommended default way:
>
> +define AICCU_INSTALL_TARGET_CMDS
> + $(MAKE) -C $(@D) DESTDIR=$(TARGET_DIR) install
> +endef
>
> This needs then the Makefile patch and I certainly can patch more buildroot related things into it,
> like renaming and permissions.
>
> 2. Using only the sub-level Makefile unix-console, which has a target "install", that
> only installs the aiccu binary. That would be clean and easy but we would be missing
> the template for the configuration (which I always find helpful)
>
> 3. Skipping the patch for the Makefile altogether and using a better version of my first
> attempt:
>
> define AICCU_INSTALL_TARGET_CMDS
> $(INSTALL) -D -m 0755 $(@D)/unix-console/aiccu $(TARGET_DIR)/usr/sbin
> $(INSTALL) -D -m 0644 $(@D)/doc/aiccu.conf $(TARGET_DIR)/etc
> endef
>
> define AICCU_INSTALL_INIT_SYSV
> [ -f $(TARGET_DIR)/etc/init.d/S60aiccu ] || \
> $(INSTALL) -D -m 0755 $(@D)/doc/aiccu.init \
> $(TARGET_DIR)/etc/init.d/S60aiccu
> endef
Between (1) and (3) I believe it's mainly a matter of whether you think
your fixes to the Makefile can be integrated upstream into a new
release or not. If your Makefile changes can be integrated upstream and
a new release is made, we can update Buildroot to use this new release,
drop the patch, and everything is nice. On the other hand, if the
upstream is more or less dead (which the very old version number seems
to indicate), then the chances of having the patch accepted and a new
release published is rather small. In that case, doing a manual
AICCU_INSTALL_TARGET_CMDS and AICCU_INSTALL_INIT_SYSV is probably
better.
> Is there a recommendation about the Snn numbering of the init.d scripts? I have not found it in the manual.
> It should run after all internet connectivity has been established and the time has been synchronized.
Network is S40network. ntp is installed at S49ntp. So I guess something
>= 50 should be fine.
> >> +
> >> +define AICCU_PERMISSIONS
> >> + /etc/init.d/aiccu f 4755 0 0 - - - - -
> >
> > Does it really have to be setuid? That is very weird for an init script.
>
> I got the permission setting wrong, it should be only 755, the 4 was a cut&paste error from the Buildroot Documentation, I will correct that, my mistake!
You don't need to set explicit permissions if you use the
AICCU_INSTALL_INIT_SYSV method since you do an $(INSTALL) -m 0755.
Thanks a lot!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-09-05 8:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-02 23:49 [Buildroot] [PATCH 1/1] aiccu: new package Michael Rommel
2013-09-04 16:38 ` Arnout Vandecappelle
2013-09-04 20:50 ` Michael Rommel
2013-09-05 8:13 ` Thomas Petazzoni [this message]
2013-09-05 22:03 ` Michael Rommel
-- strict thread matches above, loose matches on Subject: below --
2013-09-05 21:56 Michael Rommel
2013-09-07 20:56 ` Thomas De Schampheleire
2013-09-08 11:39 ` Thomas De Schampheleire
2013-09-11 6:07 ` Arnout Vandecappelle
[not found] ` <150C0AB5-B4C6-4379-9FEE-9819278AAF69@layer-7.net>
[not found] ` <CAAXf6LWetaF-1wTWvhad-gKFc0CwLrqTKjgM_F9Seou+Pm=UWg@mail.gmail.com>
2013-09-08 15:28 ` Michael Rommel
2013-09-08 17:46 ` Thomas De Schampheleire
2013-09-08 18:28 ` Michael Rommel
2013-09-09 8:41 ` Thomas De Schampheleire
2013-09-08 21:58 Michael Rommel
2013-09-11 18:34 ` Michael Rommel
2013-09-11 19:52 ` Thomas De Schampheleire
2013-09-11 21:22 ` Arnout Vandecappelle
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=20130905101359.3be9c385@skate \
--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