[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  |
--------------------------+------------------------------

Comment (by rmccue):

 Replying to [comment:19 griffinjt]:
 > On the topic of versioning dependencies, I discussed this at length with
 a friend of mine who is a PHP/Java developer and we came up with this:
 https://github.com/bubba-h57/PHP-Library-Version-Framework. Using
 namespaces plus a factory was the only viable way we could find to fix the
 issue of class version dependencies, but that can't even be considered
 until WordPress support PHP 5.3 and most plugin devs won't be able to
 implement something like it.

 We discussed this and decided that we'd only implement it at a basic
 level, since resolving multiple versions is going to be a whole new layer
 of complexity. It then becomes the plugin's problem to ensure that they
 maintain forwards- and backwards-compatibility.

 > External plugin dependencies (e.g. commercial plugins) should also at
 least be considered should something like this make it into core. There
 doesn't need to be a specific way to handle external items but at least
 some hooks or filters to allow commercial plugins to make use of it.

 I think as long as there are filters for this, it should be fine. i.e.
 `Depends: abc def othersite:ghi` would work, I think.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/22316#comment:25>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software