@Bruno, a sane admin would typically want to install a monolithic Hue due to ease of management. Note that Hue has its own mechanism to disable (or enable) certain apps.
What do you mean exactly?
If each app pulls a different project (one pulls Apache Hive, another Apache Hadoop, another Apache Oozie and another Apache HBase), I am pretty sure any sane admin would be horrified about that.
Not if you have packaging.
We are talking about the case of having a non-explicit dependency between packages.
So how would the user know about the packages?
For example, if you don't have Hive, Beeswax will show you an error. At this point, you can go install Hive if you care about Beeswax. Or you can disable Beeswax if you don't care.
The point of packaging is to make it easy for users. If I want to install Beeswax, I obviously want Apache Hive to be pulled in as well since using Beeswax without Apache Hive does not make sense.
And what kind of message does Beeswax display? Does it tell the user which package to install for his/her platform?
And if you don't care about Beeswax and Apache Hive, why installing it in the first place?
99% of the time, people want to. (I personally haven't heard of any installation that pick-and-chooses which app to install.) We're trading off 4MB of disk space with major usability and maintenance improvement. I think it's well worth it.
In that case, it may make sense to merge them. But I am still worried about all the dependencies being pulled in.