1.9.x is a developer and tester version, it is stable enough to run but things break from time to time. New features go there.
If you feel like using 1.9, , lets use our well-known PORTAGE OVERLAY feature. Turn it on in /etc/make.conf ...
Copy to clipboard $ mkdir /usr/local/portage/www-apps/tikiwiki
$ cp /usr/portage/www-apps/tikiwiki/tikiwiki-1.8.5.ebuild \
> /usr/local/portage/www-apps/tikiwiki/tikiwiki-1.9.0_rc4.ebuild #for DR4
Now we create the "tarballs for our install from latest cvs" for our own client-service. Go to your webserver root directory and create a folder "tar".
Copy to clipboard $ cd /var/www/localhost/htdocs
$ mkdir ./tar
$ cd tar
$ wget http://de.tiki.org/tar/lastiki_BRANCH-1-9.tar.bz2
$ mv ./lastiki_BRANCH-1-9.tar.bz2 ./tikiwiki-1.9.0_rc4.tar.bz2
Finally, lets modify and emerge
Copy to clipboard $ vim /usr/local/portage/www-apps/tikiwiki/tikiwiki-1.9.0_rc4.ebuild
# edit the variables:
HOMEPAGE="http://localhost"
SRC_URI="${HOMEPAGE}/tar/${P}.tar.bz2"
# line 26 append to DIRS another value
local DIRS=" whelp"
# whelp is a directory for dumps of structures to html format, coded by LuisArgerich
Copy to clipboard $ emerge tikiwiki -pv
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[ebuild N ] www-apps/tikiwiki-1.9.0_rc4 -vhosts 0 kB [1]
Total size of downloads: 0 kB
Portage overlays:
[1] /usr/local/portage
$ emerge tikiwiki
If all goes well you are now fetching the download, first failing from official mirros, but finally downloading from the HOMEPAGE/tar/ directory we specified in the ebuild.
No information about this file ebuild and associated downloaded file we created above yet exists in our local portage tree. We need to create the digest now:
Copy to clipboard $ ebuild /usr/local/portage/www-apps/tikiwiki/tikiwiki-1.9.0_rc4.ebuild digest
$ emerge tikiwiki
As this is not a release, you will get errors about missing docs, thats ok.
All this should put a copy of Tikiwiki into /var/www/localhost/htdocs/tikiwiki, unless you use the +vhost USE flag and know what your doing with your webapp-config.
Now you should go to your tikiwiki directory and continue installation steps as usual. Create empty database, create database user, grant permissions on new database to user. Point your browser to localhost/tikiwiki/tiki-install.php. Or in tikiroot do $ ./setup.sh apache apache 02775, edit db/tiki-db.php, pipe tiki.sql into new database.
For TikiMods you will have to go on commandline and use fixperms.sh to be safe.
|