I've wrapped a quick hack as a plugin to add Google Analytics to my site. Named it "Google Analytics" and, sure enough, WP offered me to upgrade my v0.1 plugin to some random plugin from the plugin repo.

I vaguely recall it getting raised a few times around WP 2.7 to 3.0. Is there a new API available somewhere to disable this, or is the only way to avoid it still is to prefix plugin names (not their file name, but their actual name as shown in the Plugins screen) to make them unique?

In my specific use case, the plugin is in mc-ga/mc-ga.php and is named "Google Analytics", along with a few other meta fields at the beginning of the plugin file header. WP yields an update notice based on "Google Analytics" (I couldn't locate a mc-ga.php plugin file in the repo).

Does WP would allow to add an extra field I'm not aware of, e.g. a repo URL or something truly unique, so as to avoid such conflicts?

I've wrapped a quick hack as a plugin to add Google Analytics to my site. Named it "Google Analytics" and, sure enough, WP offered me to upgrade my v0.1 plugin to some random plugin from the plugin repo.

I vaguely recall it getting raised a few times around WP 2.7 to 3.0. Is there a new API available somewhere to disable this, or is the only way to avoid it still is to prefix plugin names (not their file name, but their actual name as shown in the Plugins screen) to make them unique?

In my specific use case, the plugin is in mc-ga/mc-ga.php and is named "Google Analytics", along with a few other meta fields at the beginning of the plugin file header. WP yields an update notice based on "Google Analytics" (I couldn't locate a mc-ga.php plugin file in the repo).

Does WP allow to add an extra field I'm not aware of, e.g. a repo URL or something truly unique, so as to avoid such conflicts?

I've wrapped a quick hack as a plugin to add Google Analytics to my site. Named it "Google Analytics" and, sure enough, WP offered me to upgrade my v0.1 plugin to some random plugin from the plugin repo.

I vaguely recall it getting raised a few times around WP 2.7 to 3.0. Is there a new API available somewhere to disable this, or is the only way to avoid it still is to prefix plugin names (not their file name, but their actual name as shown in the Plugins screen) to make them unique?

Edit/expanding on the question per suggestion:

In my specific use case, the plugin is in mc-ga/mc-ga.php and is named "Google Analytics", along with a few other meta fields at the beginning of the plugin file header. WP yields an update notice based on "Google Analytics" (I couldn't locate a mc-ga.php plugin file in the repo). My WP-fu is a bit rusty, but I was kind of hoping that, by now, WP would allow to add an extra field I'm not aware of, e.g. a repo url or something truly unique, so as to avoid such conflicts.

I've wrapped a quick hack as a plugin to add Google Analytics to my site. Named it "Google Analytics" and, sure enough, WP offered me to upgrade my v0.1 plugin to some random plugin from the plugin repo.

I vaguely recall it getting raised a few times around WP 2.7 to 3.0. Is there a new API available somewhere to disable this, or is the only way to avoid it still is to prefix plugin names (not their file name, but their actual name as shown in the Plugins screen) to make them unique?

In my specific use case, the plugin is in mc-ga/mc-ga.php and is named "Google Analytics", along with a few other meta fields at the beginning of the plugin file header. WP yields an update notice based on "Google Analytics" (I couldn't locate a mc-ga.php plugin file in the repo).

Does WP would allow to add an extra field I'm not aware of, e.g. a repo URL or something truly unique, so as to avoid such conflicts?

I've wrapped a quick hack as a plugin to add Google Analytics to my site. Named it "Google Analytics" and, sure enough, WP offered me to upgrade my v0.1 plugin to some random plugin from the plugin repo.

I vaguely recall it getting raised a few times around WP 2.7 to 3.0. Is there a new API available somewhere to disable this, or is the only way to avoid it still is to prefix plugin names (not their file name, but their actual name as shown in the Plugins screen) to make them unique?

I've wrapped a quick hack as a plugin to add Google Analytics to my site. Named it "Google Analytics" and, sure enough, WP offered me to upgrade my v0.1 plugin to some random plugin from the plugin repo.

I vaguely recall it getting raised a few times around WP 2.7 to 3.0. Is there a new API available somewhere to disable this, or is the only way to avoid it still is to prefix plugin names (not their file name, but their actual name as shown in the Plugins screen) to make them unique?

Edit/expanding on the question per suggestion:

In my specific use case, the plugin is in mc-ga/mc-ga.php and is named "Google Analytics", along with a few other meta fields at the beginning of the plugin file header. WP yields an update notice based on "Google Analytics" (I couldn't locate a mc-ga.php plugin file in the repo). My WP-fu is a bit rusty, but I was kind of hoping that, by now, WP would allow to add an extra field I'm not aware of, e.g. a repo url or something truly unique, so as to avoid such conflicts.