wordpress 2.0.5 ebuild

wordpress-2.0.5.ebuild (text/plain), 2.81 KB, created by Emanuele Gentili on 2006-10-30 01:50:36 UTC

# Copyright 1999-2006 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $

inherit webapp eutils

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

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=mirror://gentoo/${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}
# no patch needed anymore
#	epatch ${FILESDIR}/${PV}/login-patch.diff
}

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

	webapp_src_preinst

	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

	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/wp-admin/upgrade.php and follow
	ewarn the instructions on the screen.
	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

}