summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDanny van Dyk <kugelfang@gentoo.org>2006-03-18 11:11:10 +0000
committerDanny van Dyk <kugelfang@gentoo.org>2006-03-18 11:11:10 +0000
commite7288ce73377e38e4afa782f6c049a1b02a129c9 (patch)
tree2205fbfd0f6fe7eb5887c849ba4820ae185afb07 /www-apps
parentVersion bump, bug #122155 Version schema changes from upstream reflected here (diff)
downloadhistorical-e7288ce73377e38e4afa782f6c049a1b02a129c9.tar.gz
historical-e7288ce73377e38e4afa782f6c049a1b02a129c9.tar.bz2
historical-e7288ce73377e38e4afa782f6c049a1b02a129c9.zip
Fixed all occurences of 'ewarn *'. Marked stable on amd64 wrt Bug 125693.
Package-Manager: portage-2.1_pre6-r3
Diffstat (limited to 'www-apps')
-rw-r--r--www-apps/wordpress/ChangeLog6
-rw-r--r--www-apps/wordpress/Manifest28
-rw-r--r--www-apps/wordpress/wordpress-2.0.1.ebuild52
-rw-r--r--www-apps/wordpress/wordpress-2.0.2.ebuild54
4 files changed, 77 insertions, 63 deletions
diff --git a/www-apps/wordpress/ChangeLog b/www-apps/wordpress/ChangeLog
index b3e16adb32db..64f8fbd6675d 100644
--- a/www-apps/wordpress/ChangeLog
+++ b/www-apps/wordpress/ChangeLog
@@ -1,6 +1,10 @@
# ChangeLog for www-apps/wordpress
# Copyright 2000-2006 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/www-apps/wordpress/ChangeLog,v 1.42 2006/03/18 07:17:46 superlag Exp $
+# $Header: /var/cvsroot/gentoo-x86/www-apps/wordpress/ChangeLog,v 1.43 2006/03/18 11:11:10 kugelfang Exp $
+
+ 18 Mar 2006; Danny van Dyk <kugelfang@gentoo.org> wordpress-2.0.1.ebuild,
+ wordpress-2.0.2.ebuild:
+ Fixed all occurences of 'ewarn *'. Marked stable on amd64 wrt Bug 125693.
*wordpress-2.0.2 (18 Mar 2006)
diff --git a/www-apps/wordpress/Manifest b/www-apps/wordpress/Manifest
index c35751cc6399..4350e4cf2891 100644
--- a/www-apps/wordpress/Manifest
+++ b/www-apps/wordpress/Manifest
@@ -1,6 +1,9 @@
-MD5 ef75d578db3419b331ae2be04b4f60bc ChangeLog 8063
-RMD160 42481c73bb82e9c5864635df8be61d400e0a37cc ChangeLog 8063
-SHA256 48e48b9208573756e96f0765928b998c1c8198a1a94a161f6a34803fea1f4518 ChangeLog 8063
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+MD5 d27cc272fc2d232b1e2155fb66d9bd1c ChangeLog 8243
+RMD160 1ac657c730fd823a693d58fefa959fb90a10333a ChangeLog 8243
+SHA256 035976eeca7d4bed636e3799dbc7904b6d82d2afbd75ab11e145f0890191980d ChangeLog 8243
MD5 e7fcb7479c073a03c3cea877b8cdf74a files/digest-wordpress-2.0.1 247
RMD160 45d78d66946004769be2bf9f8ff27fd538108994 files/digest-wordpress-2.0.1 247
SHA256 5fb6b31cff16d7838a3f55380ce3805e0a20f5cd38797431a28e1a51b6e345dd files/digest-wordpress-2.0.1 247
@@ -13,9 +16,16 @@ SHA256 3f7a088aa968469652690f47a2d598bd35e8f87e741f322fcb2d5063c8c88e48 files/du
MD5 bed9c007e8ee867414a21e2da8e92b3f metadata.xml 252
RMD160 d24e7a131db6ea0d35ea0c2dd03baae2702d6fc7 metadata.xml 252
SHA256 84d416249723165c3d38594876a05ec769d0f090043030f88570d129f0199639 metadata.xml 252
-MD5 2cc945a6336fd9583ea0e704e38b5150 wordpress-2.0.1.ebuild 3028
-RMD160 4a864fcfed1b54209c2af98cdb94f4e65e039b6f wordpress-2.0.1.ebuild 3028
-SHA256 b3fe67eabb31196da16bac44896293a618a9a772d1249414f5456e75a7e806fc wordpress-2.0.1.ebuild 3028
-MD5 74708a715fcb3c1a40a3325d7912dd34 wordpress-2.0.2.ebuild 3032
-RMD160 dd8b358537028bc194fc7d08b5eabee545b3b17f wordpress-2.0.2.ebuild 3032
-SHA256 149aa6befbc884452177c9c6fc1f3111e7346ad321c398de5c6ead9394ab84c4 wordpress-2.0.2.ebuild 3032
+MD5 4e1f470f660e35df9056b0d86e028ee3 wordpress-2.0.1.ebuild 2982
+RMD160 17f3a7a72cc9076cde171a2f60e9d603efa2ffa2 wordpress-2.0.1.ebuild 2982
+SHA256 ddcf3309a5dc386e0de3deb0ed44cfd2543ea3e2195f4bbd37e341a003de99a6 wordpress-2.0.1.ebuild 2982
+MD5 b618d59622c3eb9ea8f9b52e8454149d wordpress-2.0.2.ebuild 2986
+RMD160 f83b5c3282f5125c64bed23cb5a6ddc7c10a932e wordpress-2.0.2.ebuild 2986
+SHA256 a7318d7b6d1e9b630b94cf42ca3bc02401258e0c98446445891fcccbe2306998 wordpress-2.0.2.ebuild 2986
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.4.2.2 (GNU/Linux)
+
+iD8DBQFEG+0b5mJXAu5GbtIRAj1EAJ4zoWHdd276cZqNFv367P1rtW/d5QCfSoIf
+bzKzjYm66VphZCHQnqLZT4M=
+=Uggy
+-----END PGP SIGNATURE-----
diff --git a/www-apps/wordpress/wordpress-2.0.1.ebuild b/www-apps/wordpress/wordpress-2.0.1.ebuild
index 7c9f46875ebf..b9f935fe41f9 100644
--- a/www-apps/wordpress/wordpress-2.0.1.ebuild
+++ b/www-apps/wordpress/wordpress-2.0.1.ebuild
@@ -1,6 +1,6 @@
# Copyright 1999-2006 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
-# $Header: /var/cvsroot/gentoo-x86/www-apps/wordpress/wordpress-2.0.1.ebuild,v 1.6 2006/02/22 06:39:55 killerfox Exp $
+# $Header: /var/cvsroot/gentoo-x86/www-apps/wordpress/wordpress-2.0.1.ebuild,v 1.7 2006/03/18 11:11:10 kugelfang Exp $
inherit webapp eutils
@@ -37,31 +37,31 @@ src_install() {
cp -r * ${D}${MY_HTDOCSDIR}
einfo "Done"
- ewarn *
- ewarn * Please make sure you have register_globals = off set in your /etc/apache2/php.ini file
- ewarn * 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:
- ewarn * php_flag register_globals off
- ewarn *
-
- ewarn *
- ewarn * You will need to create a table for your WordPress database. This
- ewarn * assumes you have some knowledge of MySQL, and already have it
- ewarn * installed and configured. If not, please refer to
- ewarn * the Gentoo MySQL guide at the following URL:
- ewarn * http://www.gentoo.org/doc/en/mysql-howto.xml
- ewarn * Log in to MySQL, and create a new database called
- ewarn * "wordpress". From this point, you will need to edit
- ewarn * your wp-config.php file in $DocumentRoot/wordpress/
- ewarn * and point to your database. Once this is done, you can log in to
- ewarn * WordPress at http://localhost/wordpress
- ewarn *
-
- ewarn *
- ewarn * If you are upgrading from a previous version BACK UP your
- ewarn * database. Once you are done with that, browse to
- ewarn * http://localhost/wordpress/admin/wp-upgrade.php and follow
- ewarn * the instructions on the screen.
- ewarn *
+ ewarn
+ ewarn Please make sure you have register_globals = off set in your /etc/apache2/php.ini file
+ ewarn 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:
+ ewarn php_flag register_globals off
+ ewarn
+
+ ewarn
+ ewarn You will need to create a table for your WordPress database. This
+ ewarn assumes you have some knowledge of MySQL, and already have it
+ ewarn installed and configured. If not, please refer to
+ ewarn the Gentoo MySQL guide at the following URL:
+ ewarn http://www.gentoo.org/doc/en/mysql-howto.xml
+ ewarn Log in to MySQL, and create a new database called
+ ewarn "wordpress". From this point, you will need to edit
+ ewarn your wp-config.php file in $DocumentRoot/wordpress/
+ ewarn and point to your database. Once this is done, you can log in to
+ ewarn WordPress at http://localhost/wordpress
+ ewarn
+
+ ewarn
+ ewarn If you are upgrading from a previous version BACK UP your
+ ewarn database. Once you are done with that, browse to
+ ewarn http://localhost/wordpress/admin/wp-upgrade.php and follow
+ ewarn the instructions on the screen.
+ ewarn
# handle documentation files
#
diff --git a/www-apps/wordpress/wordpress-2.0.2.ebuild b/www-apps/wordpress/wordpress-2.0.2.ebuild
index b71174a1d5fc..e75538bc46e3 100644
--- a/www-apps/wordpress/wordpress-2.0.2.ebuild
+++ b/www-apps/wordpress/wordpress-2.0.2.ebuild
@@ -1,6 +1,6 @@
# Copyright 1999-2006 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
-# $Header: /var/cvsroot/gentoo-x86/www-apps/wordpress/wordpress-2.0.2.ebuild,v 1.1 2006/03/18 07:17:46 superlag Exp $
+# $Header: /var/cvsroot/gentoo-x86/www-apps/wordpress/wordpress-2.0.2.ebuild,v 1.2 2006/03/18 11:11:10 kugelfang Exp $
inherit webapp eutils
@@ -13,7 +13,7 @@ HOMEPAGE="http://wordpress.org/"
#Download is renamed by HTTP Header as wordpress-<version number>.tar.gz
SRC_URI=mirror://gentoo/${P}.tar.gz
LICENSE="GPL-2"
-KEYWORDS="~amd64 ~hppa ~ppc ~sparc ~x86"
+KEYWORDS="amd64 ~hppa ~ppc ~sparc ~x86"
IUSE=""
RDEPEND="virtual/httpd-php
>=dev-db/mysql-3.23.23"
@@ -37,31 +37,31 @@ src_install() {
cp -r * ${D}${MY_HTDOCSDIR}
einfo "Done"
- ewarn *
- ewarn * Please make sure you have register_globals = off set in your /etc/apache2/php.ini file
- ewarn * 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:
- ewarn * php_flag register_globals off
- ewarn *
-
- ewarn *
- ewarn * You will need to create a table for your WordPress database. This
- ewarn * assumes you have some knowledge of MySQL, and already have it
- ewarn * installed and configured. If not, please refer to
- ewarn * the Gentoo MySQL guide at the following URL:
- ewarn * http://www.gentoo.org/doc/en/mysql-howto.xml
- ewarn * Log in to MySQL, and create a new database called
- ewarn * "wordpress". From this point, you will need to edit
- ewarn * your wp-config.php file in $DocumentRoot/wordpress/
- ewarn * and point to your database. Once this is done, you can log in to
- ewarn * WordPress at http://localhost/wordpress
- ewarn *
-
- ewarn *
- ewarn * If you are upgrading from a previous version BACK UP your
- ewarn * database. Once you are done with that, browse to
- ewarn * http://localhost/wordpress/admin/wp-upgrade.php and follow
- ewarn * the instructions on the screen.
- ewarn *
+ ewarn
+ ewarn Please make sure you have register_globals = off set in your /etc/apache2/php.ini file
+ ewarn 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:
+ ewarn php_flag register_globals off
+ ewarn
+
+ ewarn
+ ewarn You will need to create a table for your WordPress database. This
+ ewarn assumes you have some knowledge of MySQL, and already have it
+ ewarn installed and configured. If not, please refer to
+ ewarn the Gentoo MySQL guide at the following URL:
+ ewarn http://www.gentoo.org/doc/en/mysql-howto.xml
+ ewarn Log in to MySQL, and create a new database called
+ ewarn "wordpress". From this point, you will need to edit
+ ewarn your wp-config.php file in $DocumentRoot/wordpress/
+ ewarn and point to your database. Once this is done, you can log in to
+ ewarn WordPress at http://localhost/wordpress
+ ewarn
+
+ ewarn
+ ewarn If you are upgrading from a previous version BACK UP your
+ ewarn database. Once you are done with that, browse to
+ ewarn http://localhost/wordpress/admin/wp-upgrade.php and follow
+ ewarn the instructions on the screen.
+ ewarn
# handle documentation files
#