Bug 52157 - twiki does not install
|
Bug#:
52157
|
Product: Gentoo Linux
|
Version: 2004.1
|
Platform: All
|
|
OS/Version: All
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: web-apps@gentoo.org
|
Reported By: pylon@gentoo.org
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: twiki does not install
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2004-05-26 20:53 0000
|
First of all, the ebuilds cries for:
* Ebuilds (like this one) that use the webapp-apache.eclass need to
* be converted to use the new webapp.eclass, to be compatible with
* webapp-config.
*
* Please file a bug on http://bugs.gentoo.org/, stating that this
* ebuild needs converting to use the new approach.
Second, it does not install the content of the tar-ball but the content of /var/tmp/portage
Seems that this ebuilds needs a good rewrite...
quick fixed the ebuild
works now
Created an attachment (id=35752) [details]
twiki-20030201-r1.ebuild
Here's the new twiki ebuild.
I noticed that the current twiki ebuild has rather strange dependencies---is
that correct, or am I totally off?
I used this andit worked fine apart from a problem with the config scripts that
used the wrong config file location. The snippet of the output that complains
is:
====
* Installing from /usr/share/webapps/twiki/20030201-r1/hostroot
sed: can't read /etc/apache/conf/addon-modules/twiki.conf: No such file or
directory
You are almost done!
====
I'm guessing the the reconfig file doesn't trigger the right decision of using
apache2, which I am. twiki.conf actually exists in
/etc/apache2/conf/modules.d/97_twiki.conf but with the wrong directory location
still specified. I don't know enough web-app stuff to tell, but I'm guessing
${MY_SERVERCONFIGDIR} isn't the right variable...
The check_version function in the hook is a poor attempt to figure out which
webserver is going to be used. The proper way to do this is to export
${VHOST_SERVER}, and use that. The fix is a trivial one-liner, so let's see
what Stu says, and once it's official, I'll upload the new version.
I noticed this sort of thing is missing from the new ebuild.. Is there any way
of doing this sort of thing in the new webapp way of doing things?
sed -i -e 's:\/home\/httpd:\/var\/www:g' lib/TWiki.cfg
# sed -i -e 's:urlpath\/to:var\/www\/localhost\/htdocs:g' \
# bin/.htaccess.txt
# echo "Options ExecCGI" >> bin/.htaccess.txt
Personally, I want the ebuild to handle the .htaccess file for me :) automation
is the way to go!
Also, the 97_twiki.conf (or twiki.conf) file required a bunch of
/var/www/twiki/
to
/var/www/localhost/htdocs/twiki/
changes. Perhaps this can be built in as well?
*** Bug 62848 has been marked as a duplicate of this bug. ***
*** Bug 72345 has been marked as a duplicate of this bug. ***
Why isn't the 20030201-r1 ebuild in portage yet? It can't be any worse than
what is there now.
ehi guys, bump to webapp config!
twiki-20041030 has been committed. Old and very broken versions have been
cleaned out. The web-apps team would like to apologize for the loss of
functionality you may have experienced.
