summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRobin H. Johnson <robbat2@gentoo.org>2015-08-08 13:49:04 -0700
committerRobin H. Johnson <robbat2@gentoo.org>2015-08-08 17:38:18 -0700
commit56bd759df1d0c750a065b8c845e93d5dfa6b549d (patch)
tree3f91093cdb475e565ae857f1c5a7fd339e2d781e /www-apps/wordpress/files
downloadgentoo-56bd759df1d0c750a065b8c845e93d5dfa6b549d.tar.gz
gentoo-56bd759df1d0c750a065b8c845e93d5dfa6b549d.tar.bz2
gentoo-56bd759df1d0c750a065b8c845e93d5dfa6b549d.zip
proj/gentoo: Initial commit
This commit represents a new era for Gentoo: Storing the gentoo-x86 tree in Git, as converted from CVS. This commit is the start of the NEW history. Any historical data is intended to be grafted onto this point. Creation process: 1. Take final CVS checkout snapshot 2. Remove ALL ChangeLog* files 3. Transform all Manifests to thin 4. Remove empty Manifests 5. Convert all stale $Header$/$Id$ CVS keywords to non-expanded Git $Id$ 5.1. Do not touch files with -kb/-ko keyword flags. Signed-off-by: Robin H. Johnson <robbat2@gentoo.org> X-Thanks: Alec Warner <antarus@gentoo.org> - did the GSoC 2006 migration tests X-Thanks: Robin H. Johnson <robbat2@gentoo.org> - infra guy, herding this project X-Thanks: Nguyen Thai Ngoc Duy <pclouds@gentoo.org> - Former Gentoo developer, wrote Git features for the migration X-Thanks: Brian Harring <ferringb@gentoo.org> - wrote much python to improve cvs2svn X-Thanks: Rich Freeman <rich0@gentoo.org> - validation scripts X-Thanks: Patrick Lauer <patrick@gentoo.org> - Gentoo dev, running new 2014 work in migration X-Thanks: Michał Górny <mgorny@gentoo.org> - scripts, QA, nagging X-Thanks: All of other Gentoo developers - many ideas and lots of paint on the bikeshed
Diffstat (limited to 'www-apps/wordpress/files')
-rw-r--r--www-apps/wordpress/files/postinstall-en.txt38
-rw-r--r--www-apps/wordpress/files/postupgrade-en.txt37
2 files changed, 75 insertions, 0 deletions
diff --git a/www-apps/wordpress/files/postinstall-en.txt b/www-apps/wordpress/files/postinstall-en.txt
new file mode 100644
index 00000000000..54c97717bc3
--- /dev/null
+++ b/www-apps/wordpress/files/postinstall-en.txt
@@ -0,0 +1,38 @@
+------------------------------------------------------------------------
+INSTALLATION
+
+You will need to create a table for your WordPress database. This
+assumes you have some knowledge of MySQL, and already have it
+installed and configured. If not, please refer to the Gentoo MySQL
+guide at the following URL:
+
+http://www.gentoo.org/doc/en/mysql-howto.xml
+
+Log in to MySQL, and create a new database as well as a user with full
+access to this database. After that you will need to provide the details
+of this database and the associated user within the file
+
+${MY_INSTALLDIR}/wp-config.php
+
+Finally you should be able to log in to WordPress at
+
+http://${VHOST_HOSTNAME}/${VHOST_APPDIR}
+
+------------------------------------------------------------------------
+!!!!!!!!! SECURITY WARNING !!!!!!!!!!!
+
+Wordpress has had a history of serious security flaws. Any application
+with less widespread use but the same amount of security issues would
+have been removed from the tree.
+
+After a short period of being in the unstable tree we once again decided
+that we hard mask the package.
+
+THIS MEANS THAT THERE IS NO GUARANTEE WHATSOEVER THAT THE PACKAGE WILL
+GET UPGRADED WITHIN A REASONABLE AMOUNT OF TIME EVEN IN THE CASE OF
+SEVERE SECURITY ISSUES.
+
+We consider installing this package a severe risk to your system and
+you should keep a close eye on the common security trackers so
+that you are able to fix problems with your installation yourself if
+required.
diff --git a/www-apps/wordpress/files/postupgrade-en.txt b/www-apps/wordpress/files/postupgrade-en.txt
new file mode 100644
index 00000000000..5c7b3276db9
--- /dev/null
+++ b/www-apps/wordpress/files/postupgrade-en.txt
@@ -0,0 +1,37 @@
+------------------------------------------------------------------------
+UPGRADE
+
+
+If you are upgrading from a previous version BACK UP your database.
+
+Once you are done with that, browse to
+
+http://${VHOST_HOSTNAME}/${VHOST_APPDIR}/wp-admin/upgrade.php
+
+and follow the instructions on the screen.
+
+Note that the default theme has changed between Wordpress 2.x and 3.x,
+so if you were using the default theme, your site will fail to load after
+the upgrade. Log in to the admin interface and open the themes section to
+reset to the new default theme. If you face other troubles after the
+upgrade, you might want to look for broken plugins or themes.
+
+------------------------------------------------------------------------
+!!!!!!!!! SECURITY WARNING !!!!!!!!!!!
+
+Wordpress has had a history of serious security flaws. Any application
+with less widespread use but the same amount of security issues would
+have been removed from the tree.
+
+After a short period of being in the unstable tree we once again decided
+that we hard mask the package.
+
+THIS MEANS THAT THERE IS NO GUARANTEE WHATSOEVER THAT THE PACKAGE WILL
+GET UPGRADED WITHIN A REASONABLE AMOUNT OF TIME EVEN IN THE CASE OF
+SEVERE SECURITY ISSUES.
+
+We consider installing this package a severe risk to your system and
+you should keep a close eye on the common security trackers so
+that you are able to fix problems with your installation yourself if
+required.
+