Return-Path: 
 <bigtop-dev-return-3015-apmail-incubator-bigtop-dev-archive=incubator.apache.org@incubator.apache.org>
X-Original-To: apmail-incubator-bigtop-dev-archive@minotaur.apache.org
Delivered-To: apmail-incubator-bigtop-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 3E83D9224
	for <apmail-incubator-bigtop-dev-archive@minotaur.apache.org>;
 Mon, 26 Mar 2012 21:36:48 +0000 (UTC)
Received: (qmail 3412 invoked by uid 500); 26 Mar 2012 21:36:48 -0000
Delivered-To: apmail-incubator-bigtop-dev-archive@incubator.apache.org
Received: (qmail 3376 invoked by uid 500); 26 Mar 2012 21:36:48 -0000
Mailing-List: contact bigtop-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:bigtop-dev-help@incubator.apache.org>
List-Unsubscribe: <mailto:bigtop-dev-unsubscribe@incubator.apache.org>
List-Post: <mailto:bigtop-dev@incubator.apache.org>
List-Id: <bigtop-dev.incubator.apache.org>
Reply-To: bigtop-dev@incubator.apache.org
Delivered-To: mailing list bigtop-dev@incubator.apache.org
Received: (qmail 3366 invoked by uid 99); 26 Mar 2012 21:36:48 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Mar 2012 21:36:48 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Mar 2012 21:36:46 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id BEBB234720A
	for <bigtop-dev@incubator.apache.org>; Mon, 26 Mar 2012 21:36:26 +0000 (UTC)
Date: Mon, 26 Mar 2012 21:36:26 +0000 (UTC)
From: =?utf-8?Q?Bruno_Mah=C3=A9_=28Commented=29_=28JIRA=29?= <jira@apache.org>
To: bigtop-dev@incubator.apache.org
Message-ID: 
 <371228661.19739.1332797786782.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1036337582.18286.1332783628426.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (BIGTOP-492) make our launcher scripts recognize
 cascading defaults
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


    [ https://issues.apache.org/jira/browse/BIGTOP-492?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1323=
8869#comment-13238869 ]=20

Bruno Mah=C3=A9 commented on BIGTOP-492:
-----------------------------------

* Could you give more details regarding how you see this being done?
* How are these scripts created? populated? read?
* How do you plan on educating users about this Apache Bigtop (incubating) =
feature?
* How more complicated will debugging configurations issues will be?
* What are the benefits from a user point of view? Just avoiding exporting =
<COMPONENT>_CONF_DIR>, passing parameter -conf, overriding properties -D, e=
diting the files? Why use that when I can just points to another conf dir?
* How much complexity/layer of indirection will this feature add? Is the ad=
ded value worthwhile?

Overall I am neutral provided this does not add too much confusion/complexi=
ty/indirection.
Although I believe there are a lot more important issues with a lot more va=
lue added. But Apache Bigtop (incubating) being a volunteer based project, =
anyone can work on anything they like :)


Note: I prefer /etc/bigtop/<util>rc
               =20
> make our launcher scripts recognize cascading defaults
> ------------------------------------------------------
>
>                 Key: BIGTOP-492
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-492
>             Project: Bigtop
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 0.4.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 0.4.0
>
>
> Almost all Unix (POSIX?) command line utilities have a nice feature of re=
cognizing cascading defaults. The system-level one is typically named /etc/=
<util>rc and the user-level one is typically picked from ~/.<util>rc
> I propose that we introduce the same for all of the /usr/bin launcher scr=
ipts that we support in Bigtop. The proposed format of the rc files is that=
 of POSIX-compatible sh(1) code snippet with an overall effect of exporting=
 those variables that affect execution.
> Thoughts?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira