From: Carlos Santos <casantos@datacom.ind.br>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] modem-manager: fix test of unset variable in init script
Date: Mon, 14 May 2018 08:21:16 -0300 (BRT) [thread overview]
Message-ID: <20473345.287969.1526296876360.JavaMail.zimbra@datacom.com.br> (raw)
In-Reply-To: <20180514085706.086830e9@windsurf.home>
> From: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
> To: "Arnout Vandecappelle" <arnout@mind.be>
> Cc: "Carlos Santos" <casantos@datacom.ind.br>, "Yann Morin" <yann.morin.1998@free.fr>, "buildroot"
> <buildroot@buildroot.org>, "Aleksander Morgado" <aleksander@aleksander.es>, "Peter Korsgaard" <peter@korsgaard.com>
> Sent: Monday, May 14, 2018 3:57:06 AM
> Subject: Re: [Buildroot] [PATCH 1/2] modem-manager: fix test of unset variable in init script
> Hello,
>
> On Mon, 16 Apr 2018 17:53:25 +0200, Arnout Vandecappelle wrote:
>
>> > So I will prepare a series removing the tests from the startup scripts.
>>
>> Well, part of the position we already stated a few times in the past is that we
>> should make our sysvinit scripts conform to a pattern. So I think the optimal
>> approach is:
>>
>> 1. Update the sysvinit scripts of one or two packages to conform to this
>> pattern. Note that we have not really discussed the actual pattern, just a few
>> preferences (e.g. don't test for the existence of the daemon). So it is
>> important to update only one or two scripts so we can get convergence on the
>> desired pattern, before updating many more packages.
>>
>> 2. Document this pattern in the manual. For me, it would be sufficient to refer
>> to an existing sysvinit script rather than repeating it in the manual.
>>
>> 3. Update more packages.
>>
>> 4. Add some support to check-package to identify common mistakes in the pattern.
>
> Agreed on this plan.
>
> Anybody interested in this effort ?
I already have some scratches and will send some patches as soon as
possible. <o/
--
Carlos Santos (Casantos) - DATACOM, P&D
?Marched towards the enemy, spear upright, armed with the certainty
that only the ignorant can have.? ? Epitaph of a volunteer
next prev parent reply other threads:[~2018-05-14 11:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 16:25 [Buildroot] [PATCH 0/2] Fix/improve modem-manager init script Carlos Santos
2018-04-13 16:25 ` [Buildroot] [PATCH 1/2] modem-manager: fix test of unset variable in " Carlos Santos
2018-04-14 16:07 ` Thomas Petazzoni
2018-04-15 15:31 ` Carlos Santos
2018-04-15 18:18 ` Thomas Petazzoni
2018-04-15 18:58 ` Yann E. MORIN
2018-04-15 20:22 ` Carlos Santos
2018-04-16 15:53 ` Arnout Vandecappelle
2018-05-14 6:57 ` Thomas Petazzoni
2018-05-14 11:21 ` Carlos Santos [this message]
2018-04-13 16:25 ` [Buildroot] [PATCH 2/2] modem-manager: support a defaults file in the " Carlos Santos
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=20473345.287969.1526296876360.JavaMail.zimbra@datacom.com.br \
--to=casantos@datacom.ind.br \
--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