accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Drob (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2423) Converge Shell scripts on single implementation
Date Mon, 03 Mar 2014 16:05:22 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13918193#comment-13918193
] 

Mike Drob commented on ACCUMULO-2423:
-------------------------------------

[~ctubbsii] - I only meant to suggest checking for bashisms if we are using a non-bash shell.
That is, make sure we aren't using any bash extensions when running through {{sh}}.

Bash 3 is stable enough and featured enough that I'm fine with mandating it.

> Converge Shell scripts on single implementation
> -----------------------------------------------
>
>                 Key: ACCUMULO-2423
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2423
>             Project: Accumulo
>          Issue Type: Improvement
>    Affects Versions: 1.6.0
>            Reporter: Mike Drob
>
> 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|https://wiki.ubuntu.com/DashAsBinSh#I_am_a_developer._How_can_I_avoid_this_problem_in_future.3F]
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
useful.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message