On 12.Nov.2013, at 04:59, Max Pyziur wrote: > On Tue, 12 Nov 2013, Keith wrote: > >> On 12/11/13 10:46, Max Pyziur wrote: >>> Greetings, >>> >>> Apologies for my seeming daft naivete. > > [...] > >> >> I always install from the latest tarball from the WP site, as it's the >> latest at the time of installation. With regards to WP updates and >> versions, this is generally performed with it's own built in >> updating/upgrading mechanism which is the first thing you should check >> or do after install and on an ongoing basis - IMHO anyway. > > Makes sense. > > So what are the point of having RPMs if you can't apply it server-wide > across multiple sites?
The problem with wordpress AFAICS is that $WP_PLUGIN_DIR is not stackable, i.e. you either have central plugins or you have per installation plugins. In a central installation you want to install plugins in a central way. When doing a shared host you probably want to give your users the flexibility to install plugins themself. The algorithm would be look in the central plugindir first, if not found look in the local plugindir. Wordpress does not support this. You have have only *one* directory. For a shared environment the epel rpm seems to be pointless. -- Markus _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
