Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Laszlo Papp <lpapp@kde.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>,
	Otavio Salvador <otavio@ossystems.com.br>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] Add init script (sysv) support for busybox's ntpd
Date: Thu, 20 Mar 2014 14:30:26 +0100	[thread overview]
Message-ID: <20140320133026.GG3726@jama> (raw)
In-Reply-To: <CAOMwXhNqbCGVZiJ3GCbjboiHrMVbC1aQ9Pd65xPzbmBjFSHVUg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3119 bytes --]

On Thu, Mar 20, 2014 at 12:44:47PM +0000, Laszlo Papp wrote:
> On Thu, Mar 20, 2014 at 12:26 PM, Otavio Salvador
> <otavio@ossystems.com.br> wrote:
> > On Thu, Mar 20, 2014 at 9:16 AM, Laszlo Papp <lpapp@kde.org> wrote:
> >> On Thu, Mar 20, 2014 at 11:59 AM, Otavio Salvador
> >> <otavio@ossystems.com.br> wrote:
> >>> On Thu, Mar 20, 2014 at 8:34 AM, Laszlo Papp <lpapp@kde.org> wrote:
> >>>> On Thu, Mar 20, 2014 at 11:22 AM, Koen Kooi <koen@dominion.thruhere.net> wrote:
> >>>>>
> >>>>> Op 20 mrt. 2014, om 11:45 heeft Burton, Ross <ross.burton@intel.com> het volgende geschreven:
> >>>>>
> >>>>>> On 20 March 2014 03:26, Laszlo Papp <lpapp@kde.org> wrote:
> >>>>>>> +PEER=127.0.0.1
> >>>>>>
> >>>>>> That doesn't seem like a very useful default.  We also can't use the
> >>>>>> NTP pool by default, so this should copy the behaviour of the ntpd
> >>>>>> package in meta-networking and default to no peers, and not start if
> >>>>>> none are specified.
> >>>>>
> >>>>> And the initscript is missing LSB headers.
> >>>>
> >>>> Just like the other similar scripts.
> >>>
> >>> This does not mean we ought to make the problem worse so add it for
> >>> new ones. If you are in good mood, send a fix for the others too ;)
> >>
> >> I do not think this is a problem. Could you please point out what
> >> functionality it breaks? Send patches for the others, and I will make
> >> this cosmetic change for this one, too. Consistency is more important
> >> than a mess of different styles, especially when it comes to cosmetic
> >> changes like this.
> >
> > Koen and I think it is important. So consider this my NACK for the patch as is.
> 
> You are free to NACK without an explanation why it is important, but
> do not expect it to weigh much that way, at least in my eyes, based on
> that you are not even a maintainer as far as I know.
> 
> I also think that it is not constructive to give NACK without
> answering the questions, and only telling again "It is important".
> Please be more constructive and explain the real issue. That is a
> better way of convincing a contributor than telling the person it is
> bad what you are doing because it is bad.
> 
> There was someone today publishing a blog post how important it is to
> become pragmatic to get things done. Currently, cosmetic changes are
> just in the way of getting things done. The feature shall be more
> important than cosmetic changes. I saw this frightening away
> contributors, and features actually not getting into projects.
> 
> That being said, if you can explain your reasoning, and I find it
> reasonable and worthy, I will update it.

I don't remember the exact issue I was seeing in runtime with systemd
and SysV scripts which were missing LSB headers, but it was handling
them somehow different.

If you search meta-oe git log, then you'll find many commit messages
where LSB headers were added when e.g. importing some older recipe from
oe-classic, that's good enough reason to add them to new ntp script,
isn't it?

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  parent reply	other threads:[~2014-03-20 13:30 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-20  3:26 [PATCH] Add init script (sysv) support for busybox's ntpd Laszlo Papp
2014-03-20 10:45 ` Burton, Ross
2014-03-20 11:22   ` Koen Kooi
2014-03-20 11:34     ` Laszlo Papp
2014-03-20 11:59       ` Otavio Salvador
2014-03-20 12:16         ` Laszlo Papp
2014-03-20 12:26           ` Otavio Salvador
2014-03-20 12:44             ` Laszlo Papp
2014-03-20 13:28               ` Burton, Ross
2014-03-20 16:28                 ` Koen Kooi
2014-03-20 19:01                   ` Laszlo Papp
2014-03-20 19:59                     ` Burton, Ross
2014-03-21 13:59                       ` Laszlo Papp
2014-03-21 14:39                         ` Martin Jansa
2014-03-22 14:03                           ` Laszlo Papp
2014-07-25 13:32                             ` Laszlo Papp
2015-03-01 13:48                               ` Laszlo Papp
2015-03-01 21:34                                 ` Alexandre Belloni
2015-03-02  9:54                                   ` Laszlo Papp
2014-03-20 18:49                 ` Laszlo Papp
2014-03-20 18:53                   ` Otavio Salvador
2014-03-20 18:53                   ` Laszlo Papp
2014-03-20 13:30               ` Martin Jansa [this message]
2014-03-20 16:42           ` Khem Raj
2014-03-20 11:34   ` Laszlo Papp
  -- strict thread matches above, loose matches on Subject: below --
2015-03-02 10:12 Laszlo Papp
2015-03-02 18:15 ` Laszlo Papp

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=20140320133026.GG3726@jama \
    --to=martin.jansa@gmail.com \
    --cc=koen@dominion.thruhere.net \
    --cc=lpapp@kde.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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