wordpress-2.0.ebuild

wordpress-2.0.ebuild (text/plain), 2.81 KB, created by Mark Shields on 2006-01-23 08:16:52 UTC

# 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-1.5.2.ebuild,v 1.9 2006/01/04 21:52:14 superlag Exp $

inherit webapp eutils

#Wordpress releases have a release name tagged on the end of the version on the tar.gz files

DESCRIPTION="Wordpress php and mysql based CMS system."
HOMEPAGE="http://wordpress.org/"
#Latest version is only available in the format!
#Download is renamed by HTTP Header as wordpress-<version number>.tar.gz
SRC_URI=http://markashields.com/mirrors/gentoo-ebuild-files/${P}.tar.gz
LICENSE="GPL-2"
KEYWORDS="amd64 ~hppa ppc sparc x86"
IUSE=""
RDEPEND="virtual/httpd-php
	 >=dev-db/mysql-3.23.23"

DEPEND="${DEPEND} ${RDEPEND}"

S="${WORKDIR}/${PN}"

src_unpack() {
	unpack ${A}
}

src_install() {
	local docs="license.txt readme.html"

	webapp_src_preinst

	# remove wp-admin/templates.php (XSS exploit).  See bug #88926.
	#rm -f wp-admin/templates.php
	#cp ${FILESDIR}/dummy-templates.php wp-admin/templates.php

	einfo "Installing main files"
	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 *


	# handle documentation files
	#
	# NOTE that doc files go into /usr/share/doc as normal; they do NOT
	# get installed per vhost!

	dodoc ${docs}
	for doc in ${docs} INSTALL; do
		rm -f ${doc}
	done

	# Identify the configuration files that this app uses
	# User can want to make changes to these!
	webapp_serverowned ${MY_HTDOCSDIR}/index.php
	#webapp_serverowned ${MY_HTDOCSDIR}/wp-layout.css
	webapp_serverowned ${MY_HTDOCSDIR}/wp-admin/menu.php
	webapp_serverowned ${MY_HTDOCSDIR}

	# Identify any script files that need #! headers adding to run under
	# a CGI script (such as PHP/CGI)
	#
	# for wordpress, we *assume* that all .php files need to have CGI/BIN
	# support added

	# post-install instructions
	#webapp_postinst_txt en ${FILESDIR}/1.2/postinstall-en.txt

	# now strut stuff
	webapp_src_install

}