From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] attempt to make make.sh more shellcheck compliant
Date: Fri, 12 Apr 2019 17:06:00 +0000 [thread overview]
Message-ID: <60a1f77a-d07b-be5a-be7c-9d5a050d2353@ipfire.org> (raw)
In-Reply-To: <4AE772C7-BAA2-4A28-8D4F-359DDC081A12@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1404 bytes --]
Hello Michael,
> Hello,
>
> NACK.
>
> I get your intention with this, but I do not think that the result is usable.
>
> It is a simple as that nobody ends a line with a ; in shell. I do not want to edit the script that way in the future. This is not how people write shell.
Since there are some lines ending with a semicolon in the script, I guess it
makes more sense to adjust these now, so we stay consistent in general.
>
> There might be some unquoted variables in this, but I really cannot find them in this patch.
Okay, I will hand in another patch for them, so they are clearly visible.
>
> I think there is a much bigger value in manually auditing code and understand what it does and if it does it in the right way. A lexical analysis does not improve quality.
The script consists of almost 1950 lines. You are certainly right, but an
automated analysis seemed to be the only way we can improve code quality a
bit - as a full analysis requires too much time.
>
> What you are doing here is making this compatible with other shells which will never be called because the first line says #!/bin/bash. At the end of the day, this script does not even need to be portable because it won’t run on any other platforms apart from Linux.
Okay.
>
> -Michael
Thanks, and best regards,
Peter Müller
--
The road to Hades is easy to travel.
-- Bion of Borysthenes
prev parent reply other threads:[~2019-04-12 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 16:13 Peter Müller
2019-04-12 14:51 ` Michael Tremer
2019-04-12 17:06 ` Peter Müller [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=60a1f77a-d07b-be5a-be7c-9d5a050d2353@ipfire.org \
--to=peter.mueller@ipfire.org \
--cc=development@lists.ipfire.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