All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Organov <sorganov@gmail.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/openvpn: get rid of -e in S60openvpn shebang
Date: Sat, 04 Feb 2023 23:52:21 +0300	[thread overview]
Message-ID: <875ych17cq.fsf@osv.gnss.ru> (raw)
In-Reply-To: <20230204143948.GB24755@scaer> (Yann E. MORIN's message of "Sat,  4 Feb 2023 15:39:48 +0100")

"Yann E. MORIN" <yann.morin.1998@free.fr> writes:

> Sergey, All,
>
> On 2023-02-04 16:47 +0300, Sergey Organov spake thusly:
>> The -e switch makes the script terminate on error from
>> start-stop-daemon, rendering unreachable the code that checks the exit
>> status.
>> 
>> There is no need in the -e switch in the first place either, as the
>> script takes care of errors handling.
>> 
>> Signed-off-by: Sergey Organov <sorganov@gmail.com>
>
> Applied to master, thanks.

Thank you in turn!

>
> However, this script has a lot of coding style issues:
>
>     $ ./utils/check-package 
>     package/openvpn/S60openvpn:14: should be indented with tabs (http://nightly.buildroot.org/#adding-packages-start-script)
>     package/openvpn/S60openvpn:15: should be indented with tabs (http://nightly.buildroot.org/#adding-packages-start-script)
>     package/openvpn/S60openvpn:16: should be indented with tabs (http://nightly.buildroot.org/#adding-packages-start-script)
>     package/openvpn/S60openvpn:17: should be indented with tabs (http://nightly.buildroot.org/#adding-packages-start-script)
>     package/openvpn/S60openvpn:18: should be indented with tabs (http://nightly.buildroot.org/#adding-packages-start-script)
>     package/openvpn/S60openvpn:21: should be indented with tabs (http://nightly.buildroot.org/#adding-packages-start-script)
>     [...]
>     package/openvpn/S60openvpn:0: DAEMON variable not defined (http://nightly.buildroot.org/#adding-packages-start-script)
>
> Could you look into bringing this old script up to today's standards,
> please?

Sorry, probably not me, as I'm currently using rather old buildroot
version, and it'd be problematic for me to check such changes against
the mainline.

Best regards,
-- Sergey Organov
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-02-04 20:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-04 13:47 [Buildroot] [PATCH] package/openvpn: get rid of -e in S60openvpn shebang Sergey Organov
2023-02-04 14:39 ` Yann E. MORIN
2023-02-04 20:52   ` Sergey Organov [this message]
2023-02-14 16:17 ` Peter Korsgaard

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=875ych17cq.fsf@osv.gnss.ru \
    --to=sorganov@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=yann.morin.1998@free.fr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.