From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] fake-hwclock: new package
Date: Tue, 14 Aug 2018 16:39:55 +0200 [thread overview]
Message-ID: <20180814143955.GI7915@scaer> (raw)
In-Reply-To: <20180814160032.5d2bfce8@windsurf>
Thomas, Christopher, All,
On 2018-08-14 16:00 +0200, Thomas Petazzoni spake thusly:
> 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.
Don't add an option; always install it.
Unless there is a *very* good reason not to (e.g. security
considerations), in which case a rationale must be provided.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-08-14 14:39 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 ` [Buildroot] [PATCH 1/3] fake-hwclock: " Thomas Petazzoni
2018-08-14 14:39 ` Yann E. MORIN [this message]
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=20180814143955.GI7915@scaer \
--to=yann.morin.1998@free.fr \
--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