[wp-trac] [WordPress Trac] #22303: Please parse a "vendor" file
WordPress Trac
noreply at wordpress.org
Tue Oct 30 04:37:58 UTC 2012
#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 |
-------------------------+------------------------------
Comment (by MikeSchinkel):
Replying to [comment:9 scribu]:
> Actually, to comply with their guidelines, they'd have to delete the
bundled library, so they'd have to intercept the update process anyway, so
that argument is moot.
I honestly don't understand how the ''"bundled library"'' concern matters
here either way; WordPress is not shipped as a library. What ''"bundled
library"'' are we talking about here? I seriously don't get how this
applies.
Replying to [comment:10 scribu]:
> And, like dd32, I would never recommend users install WordPress via a
package manager, because they're almost always out of date by one or more
major releases.
That's not the point. The options as per @remicollet's comments are 1.)
WordPress support Fedora's inclusion of WordPress or 2.) Fedora forks
WordPress and maintains the fork which may or may not have the quality of
WordPress core.
So whether or not you recommend users install via a package manager is
orthogonal to the discussion. And with the auto-notices for upgrades and
one-click upgrades, installing an older version really becomes a moot
point. And after the one-click upgrade the `vendor.php` file that supports
the distro would remain.
What is relevant is ''"Can Fedora ship a non-forked version of
WordPress?"'' To do that Fedora needs a only tiny bit of help from
WordPress.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/22303#comment:12>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list