[wp-hackers] Plugin dependency checking

[Shane A. Froebel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

My API makes sure the correct versions are installed and also installed
before it gets activated.

I have a unit-test case file. I am starting the integration with the core.

scribu wrote:
> On 6/17/09, Mike Schinkel <mikeschinkel at newclarity.net> wrote:
>> But the problem again is what happens when two different plugins define the
>> same interface differently? That's where the registry comes in. The function
>> 'akismet_define_interface' would NEVER be called if it is defined in the
>> registry, so plugin devs would be forced to ensure their definition would
>> match the one in the registry (which is a good thing.) OTOH if a developer
>> is developing locally with no Internet connection, or the registry web
>> service was down, WP could fall back to the local definition.
> 
> For now, I'd just like to say that having to call a remote registry
> for each plugin, on each page load, by default, is a *very* bad ideea.
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQIcBAEBAgAGBQJKOSOyAAoJEChMcQvNqPqmezIQAJwJGctjX3lX5UqED1kleQnW
w/7xsURQvC7AtZdmOvy9qJX829qltT2+UYqtcEveZwui1aKLJ/SKABPJ9Hb8Z3NR
QknF9KcG3BiOGqOxn1uvm9+h7xm8FQ+VANvsZ6j9nP9QYSPJIlkcVKcg4nqr5tc7
rk07i81jqWXXTEQT+dPIZ0YMEVQxt3EuqlNhXDipF4B9xo+QvJ0WlzV160iDkkE3
yZWNP1VXxZhJMB1rJO9tgimYMpUtTU8X4IQ/qSvzoBmSdHSeH5tF+CXc504aSYxA
BBEXSgZ8w4Fi4mD5PmEK+ZZz3dSgyq6/OWrhEOe/O5QqRknE126c9KrCB5whJCiv
vmiDZfhLTGU8QoMBEsHHBlB+uxXIpes4PqyVHLbe3cSHsFfLS6NS5q9CIpD+XAPq
3bu2Xy0ncFipvVzcj7vtVGDwudJq2Au758vWzhzZz5LXf6F9BYWluTCFwyxQUqWC
d1zjRhWgBPeNGm91rDzk0Cdi+n+AmYeuk2chzgeWiatpQSs0t2i9j6u8Ex1ZoDc2
lXW1ui2LomhommKJaONSXCxQiFcHgDAJtWXv30DkIb3YdlSgYaepyVxcOA5r19i+
XwaRgA6d5AGD5WTFylM7ejKwqB1J1j35UNPMnhmFXsA0uCxbqV6B/qaXDXV85Nm+
kJECarIsS8NWZNalfIja
=c8Ed
-----END PGP SIGNATURE-----