From: Phil Blundell <philb@gnu.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH v2 1/3] meta-systemd: Move ntp recipes to 'meta-networking' sublayer
Date: Wed, 31 Oct 2012 12:22:24 +0000 [thread overview]
Message-ID: <1351686144.13864.104.camel@phil-desktop> (raw)
In-Reply-To: <CAP9ODKqnTYfBa84642qQGzVigVzrsPQuhqvizz1smKmS=Trdww@mail.gmail.com>
On Wed, 2012-10-31 at 10:15 -0200, Otavio Salvador wrote:
> On Wed, Oct 31, 2012 at 10:11 AM, Phil Blundell <philb@gnu.org> wrote:
> > On Wed, 2012-10-31 at 12:43 +0100, Martin Ertsås wrote:
> >
> >> for now I guess we can just use pool.ntp.org
> >
> >
> > I'm not sure that this is a very good idea. The pool.ntp.org
> > documentation is fairly explicit that they don't want this:
> >
> >
> > You must absolutely not use the default pool.ntp.org zone names
> > as the default configuration in your application or appliance.
>
> So how we'll fix it? We need to fix it somehow. So give us an alternative to us.
It's not entirely obvious to me that it really does need to be fixed all
that urgently, at least not in the default metadata. The sky is
probably not going to fall in if you ship a service file which doesn't
sync with NTP by default.
In particular, if it's been broken in meta-oe for however long up to
this point, I don't entirely understand why moving the recipe to
meta-networking suddenly means that fixing this issue is super-important
or why the two things need to be done at the same time.
But, anyway, see other email I just sent for a handful of alternatives.
p.
prev parent reply other threads:[~2012-10-31 12:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 11:08 [meta-oe][PATCH v2 1/3] meta-systemd: Move ntp recipes to 'meta-networking' sublayer Otavio Salvador
2012-10-31 11:08 ` [meta-oe][PATCH v2 2/3] meta-systemd: meta-networking: ntp: Update bbappend to 4.2.6p5 Otavio Salvador
2012-11-22 6:22 ` Anders Darander
2012-11-22 10:35 ` Paul Eggleton
2012-10-31 11:08 ` [meta-oe][PATCH v2 3/3] freerdp: Bump SRCREV to 1.0.2 snapshot of 2012-10-30 Otavio Salvador
2012-10-31 11:43 ` [meta-oe][PATCH v2 1/3] meta-systemd: Move ntp recipes to 'meta-networking' sublayer Martin Ertsås
2012-10-31 11:52 ` Anders Darander
2012-10-31 12:02 ` Otavio Salvador
2012-10-31 12:11 ` Phil Blundell
2012-10-31 12:09 ` Martin Ertsås
2012-10-31 12:19 ` Phil Blundell
2012-10-31 12:29 ` Otavio Salvador
2012-10-31 12:38 ` Phil Blundell
2012-10-31 12:40 ` Otavio Salvador
2012-10-31 12:45 ` Phil Blundell
2012-10-31 12:52 ` Otavio Salvador
2012-10-31 12:32 ` Burton, Ross
2012-10-31 12:15 ` Otavio Salvador
2012-10-31 12:22 ` Phil Blundell [this message]
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=1351686144.13864.104.camel@phil-desktop \
--to=philb@gnu.org \
--cc=openembedded-devel@lists.openembedded.org \
/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