The 3 possible ideas in the post are:
1. Make wesnoth depend on wesnoth-music, wesnoth-editor and the campaigns. However, some people might not want music, campaigns and editors.
2. Make a "wesnoth-all" metapackage which depends on wesnoth and the music, editor and campaigns. However, you would instinctively install the wesnoth package rather than wesnoth-all, unless you knew whay you were doing, so few people would use it.
3. Rename wesnoth to wesnoth-base, and make a metapackage called wesnoth which depends on wesnoth-base and the music, editor and campaigns.
No. 3 seems to be the best option.
I think that these changes should be implemented in feisty.
I had a simmilar idea: http:// ubuntuforums. org/showthread. php?p=1902111# post1902111
The 3 possible ideas in the post are:
1. Make wesnoth depend on wesnoth-music, wesnoth-editor and the campaigns. However, some people might not want music, campaigns and editors.
2. Make a "wesnoth-all" metapackage which depends on wesnoth and the music, editor and campaigns. However, you would instinctively install the wesnoth package rather than wesnoth-all, unless you knew whay you were doing, so few people would use it.
3. Rename wesnoth to wesnoth-base, and make a metapackage called wesnoth which depends on wesnoth-base and the music, editor and campaigns.
No. 3 seems to be the best option.
I think that these changes should be implemented in feisty.