Why is task-base-wifi/bluetooth unconditionally included?

[Matt Darland]

RDEPENDS_task-base unconditionally brings in task-base-wifi and 
task-base-bluetooth regardless of machine/distro settings, etc. This requires 
kernels to be built with wireless extensions (because madwifi package insists 
on it), even if the device has no wireless capability.

There is an anonymous python function in task-base.bb that looks like it will 
intelligently include the right task-base-wifi/bluetooth based on 
machine/distro settings.

Is there a reason why this was unconditionally added to task-base RDEPENDS? If 
I take it out in my local overlay will something subtle break?

----
Thanks