[
https://issues.apache.org/jira/browse/BIGTOP-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238869#comment-13238869
]
Bruno Mahé edited comment on BIGTOP-492 at 3/26/12 9:34 PM:
------------------------------------------------------------
* 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)
specific 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,
editing 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 added
value worthwhile?
Overall I am neutral provided this does not add too much
confusion/complexity/indirection.
Although I believe there are a lot more important issues with a lot more value
added. But Apache Bigtop (incubating) being a volunteer based project, anyone
can work on anything they like :)
Note: I prefer /etc/bigtop/<util>rc
was (Author: bmahe):
* 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,
editing 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 added
value worthwhile?
Overall I am neutral provided this does not add too much
confusion/complexity/indirection.
Although I believe there are a lot more important issues with a lot more value
added. But Apache Bigtop (incubating) being a volunteer based project, anyone
can work on anything they like :)
Note: I prefer /etc/bigtop/<util>rc
> 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
> recognizing 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 scripts
> 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 administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
