accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Drob (JIRA)" <>
Subject [jira] [Updated] (ACCUMULO-2423) Converge Shell scripts on single implementation
Date Tue, 04 Mar 2014 15:45:22 GMT


Mike Drob updated ACCUMULO-2423:

    Attachment: ACCUMULO-2423.v1.patch.txt

Attached is my first cut at implementing best practices for our shell scripts.

This patch includes the following changes:
* Standardize interpreter line on '#! /usr/bin/env foo'
* Replace `...` with $(...) in bash scripts
* Replace \[...] with \[\[...]] in bash scripts
* Replace = with == in \[\[...]] in bash scripts

> Converge Shell scripts on single implementation
> -----------------------------------------------
>                 Key: ACCUMULO-2423
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>    Affects Versions: 1.6.0
>            Reporter: Mike Drob
>         Attachments: ACCUMULO-2423.v1.patch.txt
> Do we want to have a stated dependency on a particular shell? Most of our scripts explicitly
use bash, but some use sh. Most scripts invoke {{#\!/usr/bin/env bash}} but some do {{#\!/bin/bash}}
or other crazy things.
> I don't have a particular preference which way we go, but I'd like to see us standardize
one way or the other.
> If we use {{/bin/sh}}, then we can run everything through the [checkbashisms|]
script (also available for other distros)
> If we go the other way, and switch everything to bash, then we can run them through {{ksh
-n}} for deprecation warnings. I know that's a different shell, but they're still moderately

This message was sent by Atlassian JIRA

View raw message