[wp-trac] [WordPress Trac] #23912: Add Composer package description

WordPress Trac noreply at wordpress.org
Fri Oct 18 00:06:30 UTC 2013


#23912: Add Composer package description
------------------------------------+-----------------------------
 Reporter:  Rarst                   |       Owner:
     Type:  enhancement             |      Status:  new
 Priority:  normal                  |   Milestone:  Future Release
Component:  General                 |     Version:  3.5
 Severity:  trivial                 |  Resolution:
 Keywords:  has-patch dev-feedback  |
------------------------------------+-----------------------------

Comment (by rmccue):

 Replying to [comment:55 bpetty]:
 > Some notes about [attachment:23912.6.patch]:

 I am +1 on this patch.

 > ext-zlib: I think this should probably just be in "require" (but I left
 it as 'suggest' in this patch), PclZip will just die() if it's not
 available (and the ZIP uploaders still don't even check if it's available
 first before offering an upload form). Also, it's used frequently in core
 for adding compression support for scripts, styles, RSS feeds, and the
 HTTP API. Both ZipArchive and PclZip use it during decompression of
 plugin, theme, language pack, and upgrade ZIPs.

 +1 on requiring this.

 > SimplePie requires ext-xml, and won't work otherwise (correct me if I'm
 wrong Ryan).

 Correct, although it will use ext-dom in other places (not used by core)
 if available, as well as ext-simplexml. XML is such a pain.

 ----

 Replying to [comment:57 bpetty]:
 > As Ryan has also expressed, there really is no context under which you
 would include WordPress as a package dependency through Composer. It's not
 a library, and none of it can even be loaded by the autoloader, which is
 how Composer dependencies are designed to be included without relying on
 known installation paths.

 +1. My issue is that adding anything else is trying to make WordPress
 something it's not, and trying to use Composer to handle everything. A
 library is decidedly not a project and vice versa, so they naturally have
 different handling.

 ----

 Replying to [comment:59 TJNowell]:
 > I would also take note of a similar file, doing a similar job that gets
 used by a tool with the same purpose as Composer albeit written in
 javascript:
 >
 > ​http://develop.svn.wordpress.org/trunk/package.json

 Note that this is part of the build tools, not part of the project itself,
 so it's not really relevant. Grunt isn't part of WordPress any more than
 PHPUnit is, they're just both part of our development process.

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


More information about the wp-trac mailing list