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

Mark Grover commented on BIGTOP-1093:
-------------------------------------

For spark in Bigtop, there are 3 packages - spark, spark-master and 
spark-worker. The 'spark' package contains all core bits and default 
configuration pertaining to Spark. The 'spark-master' and 'spark-worker' 
package contain init scripts for the Spark worker and master services.

While I think it's still a good idea to solve this naming conflict problem for 
all bigtop packages generally, in Spark's case in particular, I personally 
prefer renaming the 'spark' package to 'spark-core' package since that's closer 
to what it delivers anyways. Whatever decision we make about all packages for 
naming conflicts (like say prefixing all bigtop packages with 'bigtop-') will 
apply to spark as well, just like it would apply to any other bigtop package 
but perhaps, we should solve this immediate conflict by renaming the 'spark' 
package to 'spark-core' which in my opinion, is a better name anyways. Due of 
this conflict, it's not possible to install spark on Debian based systems today.

What do you folks think?

> decide on package naming scheme
> -------------------------------
>
>                 Key: BIGTOP-1093
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1093
>             Project: Bigtop
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 0.7.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>            Priority: Blocker
>             Fix For: 0.8.0
>
>
> Recently, more and more Linux distributions started to package bits and piece 
> of the Bigtop stack natively. This leads to package name conflicts and also 
> potentially file-name conflicts. Bigtop needs to figure out a way of 
> co-existing with these.
> More here: 
> http://mail-archives.apache.org/mod_mbox/bigtop-dev/201309.mbox/%3CCA%2BULb%2BvO8NSA_hnbg8RhWV8-boCe03NcELDAE8n19_%2B2c-oppA%40mail.gmail.com%3E



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to