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

Making WordPress.org noreply at wordpress.org
Sat Apr 8 00:12:32 UTC 2023


#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 jsmoriss):

 > Part of the deal with hosting plugins on WordPress.org is that the
 plugin updates be available from WordPress.org. if the dependency does not
 exist here, then the plugin is invalid, because the dependency is not
 available here.

 So if plugin ABC depends on DEF, but plugin DEF hosted on github (for
 example), then wordpress.org will refuse the submission of plugin ABC, and
 if previously hosted on wordpress.org, once plugin ABC declares its
 dependency on DEF, it will be pulled from the repo. Is that correct?

 Note that this is not a situation with any of my own plugins, but it
 struck me as wordpress.org creating a walled garden, which has not been
 the previous approach of the wordpress.org repo.

 js.

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


More information about the wp-meta mailing list