[wp-trac] [WordPress Trac] #22303: Please parse a "vendor" file
WordPress Trac
noreply at wordpress.org
Mon Oct 29 21:04:34 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: dev-feedback |
--------------------------+------------------------------
Changes (by MikeSchinkel):
* cc: mike@… (added)
Comment:
This seems like a perfectly reasonable request and approach, although the
discussion of bundling confused me and I wonder if it's mention was a
distraction from the goal of the ticket?
Unless I misunderstand the request this simply allows Fedora or any other
distro to take a '''standard WordPress version download''' and add distro-
specific support and/or optimizations in a separate file that the distro
maintains. Using his example I can see better SMTP integration as being
very helpful; I know having to deal with that on a plugin level can be a
real pain for non-technical end-user bloggers. So this seems like a much
better approach than forcing the distro to create a fork which means they
then have to intercept the WordPress core update process to reapply their
fork which I can see as very problematic.
With his approach this vendor file can go in the `/wp-content/` directory
and updates simply won't affect it. I can see potential security concerns
if the vendor file needs to be updated but would think a discussion of how
to address those concerns would be more productive than having them fork
and maintain a WordPress download.
Also, I think the proposal I made on #22251 would be helpful if this
proposal gets any traction.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/22303#comment:6>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list