[wp-trac] [WordPress Trac] #22303: Please parse a "vendor" file

[WordPress Trac]

#22303: Please parse a "vendor" file
--------------------------------+------------------------------
 Reporter:  remicollet          |       Owner:
     Type:  enhancement         |      Status:  new
 Priority:  normal              |   Milestone:  Awaiting Review
Component:  General             |     Version:
 Severity:  normal              |  Resolution:
 Keywords:  close dev-feedback  |
--------------------------------+------------------------------
Changes (by dd32):

 * keywords:  close => close dev-feedback


Comment:

 Replying to MikeSchinkel:
 > I honestly don't understand how the "bundled library" concern matters
 here either way;

 The concern is that !WordPress includes external libraries such as
 SimplePie and PHPMailer, Fedora, amongst others, states that external
 libraries such as these are not permitted to be included within a Package,
 "!WordPress" package in this instance.

 The request is for a auto-loaded file which can define alternate
 filesystem paths to the packages which !WordPress uses, removing control
 of the version of the library !WordPress uses.

 Fedora can ship a non-modified version of !WordPress if they wish, they
 just choose not to. They would have to fork !WordPress regardless to
 remove the External libraries from the package, and even then, we have the
 fact that we don't name external library files the same as some of the
 projects (ie. `class-phpmailer.php`) which would further complicate
 matters when it's a library split between multiple files (SimplePie for
 example)


 > 2.) Fedora forks WordPress and maintains the fork which may or may not
 have the quality of WordPress core.

 Any forked copy or distributed copy of !WordPress which uses external
 libraries not controlled/included by us, may not have the same quality of
 !WordPress core, may have other bugs, or may not work as intended - this
 is something we loose control of by handing control of the external
 libraries over to someone else.

 A prime example of this is when a Plugin or Theme replaces jQuery with a
 different version and all hell breaks loose - this is exactly the same,
 except instead of a JS bug, it's a PHP or application bug - potentially
 not reproducible in a stock install and only reproducible on the exact
 same package setup as the reporter - I believe we've already seen at least
 one bug report which was caused by a debian modification (The answer was
 "Uninstall it, re-install it from the official source, & you won't have
 any more problems").

 I'm not against making life easier for those maintaining !WordPress
 packages, I'm just against making a change which potentially makes
 !WordPress not as stable, or as user friendly as it already is.

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