What steps will reproduce the problem?
1. Install it
2.
3.

What is the expected output? What do you see instead?
No install package should be missing dependencies.  While it's probably easier for the author/maintainer to toss everything into one package, it borks Curse Client installs when you try to delete the bar addon related components that a user doesn't need.  Disabling the two other addons through WoW's addon UI is an undesired complication as well - many, if not most, users don't want to have addon lists cluttered with unused and disabled addons.

For example: I have Titan Panel.  I use the LDB launcher for Fishing Buddy.  I'm forced to download 2 other addons that don't work on my system, and if I delete those folders (for infobar and fubar) then Curse Client flags the whole package as being modified, which has a couple of inconvenient and undesired side-effects.

If you can't, for whatever reason, maintain separate packages, let me know.  I'll split off the project and maintain the 3 packages separately so users don't have to be inconvenienced.  An alternate solution is to repackage the 3 bar launcher addons as one addon - and have code check for the existence of dependent displays/launchers, then branch and load the launcher for the detected bar addon / LDB display.  I personally don't like this solution as it adds some heft to the addon, but it's better than the current state.