Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/4277#issuecomment-72114226
This one is fairly innocuous, but in common with other issue with the
Debian packaging within Spark, we don't have really good answers as to what is
the "right" thing to do. That's because this packaging was never intended to
strictly follow Debian or Ubuntu packaging requirements, but rather as an
expedient to meet a particular set of tool-based deployment needs. Now we are
getting requests from others with different needs, desires and expectations.
Fulfilling all of those requests, if it can even be done, is probably more than
we want to take on and maintain.
If the Debian packaging is to remain in the Spark distribution, then we are
probably going to have to leave it in a state that is broken from the
perspective of many users and offer some variant on the excuse that this
shouldn't be expected to be more than a functioning template that users can
customize to meet their particular needs.
The larger question, though, is whether we should keep it at all or instead
remove the Debian packaging entirely and hand over all Spark packaging concerns
to Apache Bigtop and other Spark Distributions.
@pwendell
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
