From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] fake-hwclock: new package
Date: Tue, 14 Aug 2018 16:00:32 +0200 [thread overview]
Message-ID: <20180814160032.5d2bfce8@windsurf> (raw)
In-Reply-To: <20180810144635.16182-1-chrismcc@gmail.com>
Hello,
Yann, Arnout, Peter, there is a question below.
Christopher, there are some review comments as well.
On Fri, 10 Aug 2018 07:46:34 -0700, Christopher McCrory wrote:
> +if BR2_PACKAGE_FAKE_HWCLOCK
> +config BR2_PACKAGE_FAKE_HWCLOCK_CRONJOB
> + bool "install fake-hwclock cronjob"
> + help
> + Hourly cronjob to save current timestamp
What should be our policy for cronjobs ? I'm not sure we currently have
packages that install cronjobs. What should we do? Install
unconditionally? Have a sub-option?
I would personally lean towards installing unconditionally, but I'd
like to have others opinions before applying.
> +FAKE_HWCLOCK_VERSION = v0.11
> +FAKE_HWCLOCK_SITE = https://git.einval.com/git/fake-hwclock.git
> +FAKE_HWCLOCK_SITE_METHOD = git
> +FAKE_HWCLOCK_LICENSE_FILES = COPYING
> +FAKE_LICENSE = GPL-2.0
This variable is wrong: it should be FAKE_HWCLOCK_LICENSE. Also, we
prefer to have it before the LICENSE_FILES variable.
> +define FAKE_HWCLOCK_NO_LSB
> + $(SED) 's at . /lib/lsb/init-functions@#. /lib/lsb/init-functions@' \
> + $(@D)/debian/fake-hwclock.init
> +endef
This should be done by a patch.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-08-14 14:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 14:46 [Buildroot] [PATCH 1/3] fake-hwclock: new package Christopher McCrory
2018-08-10 14:46 ` [Buildroot] [PATCH 3/3] perl-cgi: " Christopher McCrory
2018-08-14 3:45 ` François Perrad
2018-08-14 14:00 ` Thomas Petazzoni [this message]
2018-08-14 14:39 ` [Buildroot] [PATCH 1/3] fake-hwclock: " Yann E. MORIN
2018-08-14 17:44 ` Christopher McCrory
2018-08-14 23:04 ` 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=20180814160032.5d2bfce8@windsurf \
--to=thomas.petazzoni@bootlin.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