Bug#748383: ITP: bash8 -- bash script style guide checker
Andreas Metzler <email@example.com> writes:
> On 2014-05-17 Thomas Goirand <firstname.lastname@example.org> wrote:
> > On Sat May 17 2014 02:54:13 AM EDT, Andreas Metzler <email@example.com> wrote:
> >> On 2014-05-16 Thomas Goirand <firstname.lastname@example.org> wrote:
> >>> This program attempts to be an automated style checker for bash
> >>> scripts to fill the same part of code review that pep8 does in
> >>> most OpenStack projects. It started from humble beginnings in the
> >>> DevStack project, and will continue to evolve over time.
> >> how about choosing a different package name? As a user I would
> >> expect to find bash v8 inside a "bash8" package.
Whereas this Bash user would expect a package named ‘bash8’ to install
version 8 of Bash.
Certainly ‘bash8’ carries no reliable connotation of “style checker for
> > This is a reference to "pep8" in the Python.
In the Python community, “PEP 8” carries strong connotation of “code
style conventions for Python code”. It is *only* because of that
existing connotation that a package named ‘pep8’ implies what the
The same is not true for the name ‘bash8’. It is unreasonable to expect
the average Bash user looking at package names to get a reference to
IMO, the package (source and binary) name should more explicitly carry
an implication of what the package installs. Perhaps
‘bash8-style-checker’ or the like.
\ “The cost of education is trivial compared to the cost of |
`\ ignorance.” —Thomas Jefferson |
Ben Finney <email@example.com>