On 28/11/13 18:31, Rick Thomas wrote: > > On Nov 27, 2013, at 8:12 PM, Miles Fidelman > <mfidel...@meetinghouse.net> wrote: > >> Scott Ferguson wrote: >>> The OP (in this thread) is asking about the Debian WordPress >>> package. It installs WordPress, WordPress keeps itself up-to-date >>> - i.e. it's version has nothing to do with the version number of >>> the debian installer. On 28/11/13 09:48, Scott Ferguson wrote: >>
<snipped> >> Miles Fidelman > > Thanks, Miles. > > I'll keep your advice in mind as I go forward with this project. > > Your suggestion raises the question, though, of what do I do when I > want to upgrade from Wheezy to Jessie in a year or so? Will I get a > toxic mix of Debian-wordpress and wordpress-upstream? NO! Ignore the speculation, well intended though it is. The debian installer does *not* mean you run an out-dated version of WordPress - it immediately upgrades to the current version of WordPress (and all your themes and extensions). When you first login the Dashboard shows updates available - click on the icon and you'll soon be running the freshly baked latest WordPress which is downloaded from the WordPress site. Upgrading Wheezy to the Jessie when it becomes stable, or indeed, upgrading to Testing or Unstable tomorrow won't affect the Debian installed WordPress - it will continue to be the most current version available from upstream. This is one of the reasons why it's better to use the Debian installed WordPress than downloading the tarball and dumping it somewhere. All the package does is install WordPress into the Debian standard locations. WordPress then manages it's own updates. > > In other words, am I stuck on Wheezy until I'm willing to do a > complete re-install of wordpress from scratch? No. > > Thanks! Rick > Kind regards. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5296f622.8050...@gmail.com
