[wp-trac] [WordPress Trac] #22316: Plugin Dependencies (Yet Another Plugin Dependencies Ticket)

[WordPress Trac]

#22316: Plugin Dependencies (Yet Another Plugin Dependencies Ticket)
--------------------------+------------------------------
 Reporter:  Viper007Bond  |       Owner:
     Type:  enhancement   |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Plugins       |     Version:  3.4.2
 Severity:  normal        |  Resolution:
 Keywords:  dev-feedback  |     Focuses:
--------------------------+------------------------------

Comment (by ideag):

 Replying to [comment:80 MikeSchinkel]:
 > My two cents:  Plugin Header is the way to go and then WordPress core
 should just ''"handle it."''
 >
 > @ideag: That said, how does TinyLibraries handle incompatible versions?
 Let's say I have Foo plugin and Bar plugin and they both use Baz library,
 but Foo uses 1.3 and Bar uses 2.5.   Assuming [http://semver.org/ SemVer]
 then you'd have a situation where either Foo or Bar would be run on the
 site but not Foo and Bar at the same time because their different versions
 of Baz would conflict.

 I completely agree, that this should be a part of the Core. My plugin is
 just an attempt to display one way how this could be ''handled''.

 Regarding versioning, I think WordPress should always update libraries to
 the latest ''stable'' version. If a new version of the library comes out,
 WordPress would update it the same way it updates itself, themes, plugins
 and translations. And plugin developers would need to stay up to date with
 that. The same way they have to stay up to date with core API's and Core
 version of jQuery, etc. I know that's a bit idealistic, but I think this
 would be good for the ecosystem as a whole. And Core would not need to
 deal with the mess of 12 different plugins requiring 12 different versions
 of the same library.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/22316#comment:81>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform