Node module is not marked "required", but is required by other required modules

I couldn't find the duplicate so I'm reopening this. There are 206 instances of node_list alone in the repository (core+contributions). I cycled through 50 or so of these, and none of them check for the existence of the node module. Our collective usage of the node module indicates that it is, in fact, a required module.

+1

It makes sense to me. I never really thought about it, but this is a good point. While I'm not aware of any problems with folks disabling the node module, I think it makes sense to cover our collective behinds. The code looks fine and works as expected. It just adds "node" to the required array.

Any idea of how hard it would be to fix the dependencies?

I know someone who has a nice dependency patch awaiting commit... adding a few depencies after that is trivial :P

So, what to do with this one? I recall some opposition from Goba to making node.module required. I myself would be in favour.

The patch doesn't apply anymore.

How fitting that just 5 minutes ago I got burned by this. Please commit... I see no sense in not requiring the node module. Show me a site (are there any?) that doesn't use the node module, and I'll show you a site maintainer who will know how to revert this patch, and I think that we're talking at most about .0001% of all Drupal sites. Yet serious problems do and will continue to arise because unknowing admins can disable what is arguably the central piece of Drupal functionality.

Ack, applied.