[wp-meta] [Making WordPress.org] #6921: Prepare for Plugin Dependencies

[Making WordPress.org]

#6921: Prepare for Plugin Dependencies
------------------------------+---------------------
 Reporter:  dd32              |       Owner:  (none)
     Type:  defect (bug)      |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  needs-patch       |
------------------------------+---------------------

Comment (by Otto42):

 No one is speaking about "banning" anything. Simply not serving a plugin
 thru the API and possibly showing an error message to a plugin author when
 they use an incorrect dependency is what we're really talking about here.

 If there is a dependency failure in a plugin, then we want to show an
 error to the author so they can correct it. If a plugin is submitted with
 an invalid dependency, we would want to show that error to them during the
 submission process. If a plugin is removed for cause or for whatever
 error, then we want to let any dependent plugins know about that fact.

 If dependencies are going to exist, then they need to be managed properly,
 and code needs to be created to allow them to be useful in all aspects of
 the system. Things don't get made only to be useful for core.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/6921#comment:11>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org