[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 scribu):

 Replying to [comment:19 griffinjt]:
 > While I think header comments are nice, I think a more robust API should
 be created for handling this, especially when you start getting into the
 issue of forcing activation/deactivation with dependencies.

 Header comments are preffered because they can be parsed without
 activating the plugin first.

 On the issue of forcing activation, when you specify a dependency, you say
 "I _need_ this to be active".

 If you don't need it to be active, it's not a dependency; it's a nice-to-
 have, which should be specified using a separate header or some other
 method.

 The issue is: is it safe for plugin X be auto installed and activated? For
 example, you wouldn't want BuddyPress to be auto-installed and activated,
 since it changes your site in a 100 ways.

 But, I think this should be specified by the library, with a header like
 "Provides: metabox". Besides providing a stable name for the library, it
 could also signal that it's safe to auto-activate.

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