On 9/19/16 3:36 PM, David Wright wrote:
On Mon 19 Sep 2016 at 13:43:04 (-0500), Kent West wrote:
On Mon, Sep 19, 2016 at 1:29 PM, Kent West <we...@acu.edu> wrote:
On Mon, Sep 19, 2016 at 11:53 AM, Tony Baldwin <tonybald...@gmx.com>
On 09/19/2016 12:26 PM, Miles Fidelman wrote:
On 9/19/16 12:20 PM, Tony Baldwin wrote:
I make a new user on the server for each new WP site, and then install
their WP in /home/$user/www . much simpler than having bits of it all
over the machine.
So what I'm hearing is that I should forego using apt/aptitude to install
WordPress, and just install in manually?
Neither of those people appear to reveal their update policy or how
they deal with security fixes.
I just use the built in WordPress updater - which takes care of
everything. No need to worry about whether some packager has updated
both the core and every theme and module that I use (guaranteed, they
Now, when it comes to perl based systems, such as the sympa mailing list
manager (mailman, too for that matter), - better to use cpan to install
and update all of one's perl system and modules.
As to security fixes - those are far more likely to come from upstream,
in a timely manner.
Apt is a fantastic package management system, for widely used things,
that don't change very often. For anything else, relying on human
packagers is a recipe for disaster - particularly when dealing with,
potentially, 3 layers of packaging (the upstream package, an
intermediate packaging system like cpan, and the Debian repository.)
In theory, there is no difference between theory and practice.
In practice, there is. .... Yogi Berra