I vote for 1.
I completely disagree with options 2 and 2 because of two reasons:
- First, I don't quite see the point in having both GUI and non-GUI utlities installed at the same time. In most cases, either you use the GUI or the non-GUI app :-)
- Second, having aMuleWeb in a different package from aMuleCMD or, in the worst case, having aMuleCMD considered as a "non-useful" remote aMule administartor is an error from the point that in some future, aMuleCMD should be improved to be as feature-rich as aMuleWeb (from what code reads, ir seems to me like shakraw is already working on that). aMuleCMD would be the interface with aMule in a future were core and GUI are splitted. In a not-so-far future, aMuleCMD would be the interface with all those ssh aMule users who are claiming for aMuleCMD to be "useful" ;-) So, having future in mind, I think aMuleWeb and aMuleCMD should be considered as "the same" in functional terms.
My secondary vote would be number 4, though (all or nothing, hehe ;-) )