From: "Gunnar Wrobel (wrobel)" <wrobel@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in www-apps/wordpress/files: postinstall-en.txt postupgrade-en.txt
Date: Fri, 15 Feb 2008 09:35:53 +0000 [thread overview]
Message-ID: <E1JPwz3-00061f-GF@stork.gentoo.org> (raw)
wrobel 08/02/15 09:35:53
Modified: postinstall-en.txt postupgrade-en.txt
Log:
Added wordpress-2.3.3 to the tree.
(Portage version: 2.1.4_rc7)
Revision Changes Path
1.3 www-apps/wordpress/files/postinstall-en.txt
file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/www-apps/wordpress/files/postinstall-en.txt?rev=1.3&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/www-apps/wordpress/files/postinstall-en.txt?rev=1.3&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo-x86/www-apps/wordpress/files/postinstall-en.txt?r1=1.2&r2=1.3
Index: postinstall-en.txt
===================================================================
RCS file: /var/cvsroot/gentoo-x86/www-apps/wordpress/files/postinstall-en.txt,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- postinstall-en.txt 8 Jan 2008 06:29:52 -0000 1.2
+++ postinstall-en.txt 15 Feb 2008 09:35:52 -0000 1.3
@@ -1,17 +1,6 @@
------------------------------------------------------------------------
INSTALLATION
-Please make sure you have register_globals = off set in your
-
-/etc/apache2/php.ini
-
-file.
-
-If this is not an option for your web server and you NEED it set to
-on, then insert the following in your WordPress .htaccess file:
-
-php_flag register_globals off
-
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
@@ -19,14 +8,13 @@
http://www.gentoo.org/doc/en/mysql-howto.xml
-Log in to MySQL, and create a new database called 'wordpress'. From
-this point, you will need to edit your
+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
-file.
-
-Once this is done, you can log in to WordPress at
+Finally you should be able to log in to WordPress at
http://${VHOST_HOSTNAME}/${VHOST_APPDIR}
@@ -37,13 +25,14 @@
with less widespread use but the same amount of security issues would
have been removed from the tree.
-We decided to keep the application in the unstable portage tree so that
-it get's some level of attention from our security team. Currently
-you can expect us to react within 40 days of a reported security
-problem.
-
-This still means that you might open up your installation to hackers for
-about a month after an issue has been made public. This is a severe
-risk and you should keep a close eye on the common security trackers so
+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.
1.3 www-apps/wordpress/files/postupgrade-en.txt
file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/www-apps/wordpress/files/postupgrade-en.txt?rev=1.3&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/www-apps/wordpress/files/postupgrade-en.txt?rev=1.3&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo-x86/www-apps/wordpress/files/postupgrade-en.txt?r1=1.2&r2=1.3
Index: postupgrade-en.txt
===================================================================
RCS file: /var/cvsroot/gentoo-x86/www-apps/wordpress/files/postupgrade-en.txt,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- postupgrade-en.txt 8 Jan 2008 06:29:52 -0000 1.2
+++ postupgrade-en.txt 15 Feb 2008 09:35:52 -0000 1.3
@@ -17,14 +17,15 @@
with less widespread use but the same amount of security issues would
have been removed from the tree.
-We decided to keep the application in the unstable portage tree so that
-it get's some level of attention from our security team. Currently
-you can expect us to react within 40 days of a reported security
-problem.
-
-This still means that you might open up your installation to hackers for
-about a month after an issue has been made public. This is a severe
-risk and you should keep a close eye on the common security trackers so
+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.
--
gentoo-commits@lists.gentoo.org mailing list
reply other threads:[~2008-02-15 9:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1JPwz3-00061f-GF@stork.gentoo.org \
--to=wrobel@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox