Wrong way to overwrite a menu

In everyblog.module, the function everyblog_menu() contains the following definition for a menu item:

	$blogs = array();
	$items['blog/%'] = array(
		'page callback' => 'everyblog_page',
		'page arguments' => array(1),
		'access callback' => 'everyblog_page_user_access',
		'access arguments' => array(1),
		'type' => MENU_CALLBACK,
		'file' => 'everyblog.pages.inc',
	);

That menu item is already defined from blog.module, therefore everyblog.module must implement hook_menu_alter() to alter such menu.

I hope this helps to understand the issue I am talking of.
Regards,
Kiam

Except that I'm not overwriting an existing menu since EveryBlog is incompatible with the core Blog module and expects it to be disabled.

That is not stated in the project page. I was thinking the module was just an extension for blog.module which then could co-exist with it.
If the module requires the core module to be disabled, then it should check that at runtime, and report an error in such case (the checking can be done in the implementation of hook_requirements()).

Until blog.module has not been disabled, everyblog.module is re-defining an already existing menu.

I usually put a link to the documentation page, but this time I forgot to do it.
As the documentation for the hook states, the checking can be done when the module is being installed, or when the module is being executed; in the first case, if the hook implementation returns an error code, the installation of the module gets stopped.

I am closing this issue, which is for a not supported Drupal version.