create new tag
, view all tags
Hi smile

I just installed TWiki on my Gentoo system (x86) without any problems.
Especialy intersting is, that I did not even get problems using Apache 2 (2.0.46) and Perl 5.8.0 :-)
I just followed the installation guide, and had to watch out in the config files for Apache 2 where the directorys are configured, that I use the Apache 2 syntax (for example enclosing "deny from all" in "IfModule mod_access.c" and "/IfModule"... you'll see that. I don't think, that I'll write an ebuild, because all it could do, would be to extract the TWiki-package into /home/httpd/twiki ... that's something you can do on your own wink

Have fun, Daniel (daniel_AT_troeder*de)

-- TWikiGuest - 08 Jun 2003

There now seems to be a TWiki package (ebuild) for Gentoo - maybe the packager could comment here?

The ebuild script does seem a bit odd, in that it says TWiki depends on PHP and MySQL, neither of which is true, and states that the license is LGPL-2.1 when it's actually GPL (not sure which version).

I've been developing on Perl 5.8.3 quite a lot, so I think Perl 5.8 is not a big issue these days as long as you avoid the Perl 5.8.0 'believe Red Hat when they say the locale is *.UTF-8' problem - 5.8.1 or higher is best.

-- RichardDonkin - 04 Mar 2004

I recommend staying away from the twiki gentoo ebuilds for now. No one is maintaining them with any effort and they really suck and don't use the webapp.eclass yet. You'd be safer just installing by hand.

-- DavidGrant - 25 Nov 2004

I'm the (new) Gentoo maintainer of TWiki. The ebuild hopefully doesn't suck any more. If you have any problems, please file a bug in our bugzilla.

-- RenatLumpau - 27 Jan 2006

The latest ebuild in portage is twiki-20041030-r1. Do you plan an ebuild for the new dakar release twiki-4.0.0 ?

-- TobiasRoeser - 01 Feb 2006

Latest ebuild is now up to date (4.0.4), but there doesn't seem to be a clear policy on where to serve the TWiki files from. This is what I have found:

  • The ebuild copies the TWiki files to /usr/share/webapps/twiki/4.0.4/htdocs/
  • The install script (which the ebuild recommends me to run) copies the data again to /var/www/<host>/htdocs/twiki/ (I think that you are supposed to choose <host> so that you can have different instances of TWiki running side-by-side, but it might be more to do with apache having virtual hosts which I don't know much about)
  • The HOWTO TWiki on the Gentoo wiki recommends copying the TWiki files again to /home/twiki/htdocs/

Also, the Gentoo "HOWTO TWiki" recommends creating a 'twiki' user, but then has apache owning all the files. Can we agree on a best-practice way to host TWiki on a Gentoo system and spell it out here? Can someone more knowledgable than I provide arguements/explanations on what methods are the most secure and/or easiest to work with and maintain? In addition to helping people getting their install up and running, it will make things easier for Renat to maintain and improve the ebuild. While I am no expert, I'll make a starting proposal:

  • The TWiki files should be served from /var/www/<host>/htdocs/twiki/
  • The TWiki files should be owned by the 'apache' user

-- BenWatts - 21 Jul 2006

i definitely recommend creating a twiki user and setting the files' owner to twiki, and group to apache (or httpd or www-data, or whatever it is on gentoo).

-- WillNorris - 22 Jul 2006

I'm used to install twiki under /var/www/localhost/ directly. This has some advantages.

  • You just have to understand twiki and apache to configure it, not an additional and often changing web-app-config, which is quite more complex than all the other cool and useful Gentoo tools
  • You don't have to deal with .htaccess files, to deny and therefore override allready allowed access to e.g. the data/ directory, as it would be the case if you have installed TWiki under /var/www/localhost/htdocs
  • You can install many twiki's under the same apache's virtual host, which reduces complexity. Just copy /var/www/localhost/twiki/ to e.g. /var/www/localhost/new-twiki/...
  • Apache's configuration is centrallized within one file located in /etc/apache2/modules.d/, e.g. 99_twiki.conf. This approach offers more individuall access and alias rules, too.

The Disadvantages:

  • You have to manually upgrade/update your Twiki installation

But to be reallistic, I have patched many parts of TWiki and blindly updating only parts of TWiki will not work without a big surprise, anyway.

-- TobiasRoeser - 22 Jul 2006

Iam using a custom installation of TWIki, not a Ebuild.

For anybody who runs into problems with internationalisation under gentoo, should watch some things.

first of all, you should check : http://twiki.org/cgi-bin/view/Codev/UserInterfaceInternationalisation And install all perl modules needed for your TWiki Version.

After that run "locale -a" and check, wheather your needed locales are installed. If not, use the gentoo way to create them : http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=6

after that, you have to set the exact name showed by locale -a into {Site}{Locale} and enable {UseLocale}. Both are under "Localisation" in the configure script. if you get a warning like "could not set localisation", you might have a type in the name or a missing perl module

-- MayerEugen - 15 Oct 2007

Good point about the locales needed for I18N. If you could add that Gentoo tip to the 'generating locales' part of InstallationWithI18N that would help fill that out. There's already a section covering locales for TWikiOnDebian and TWikiOnUbuntu.

-- RichardDonkin - 23 Oct 2007

Edit | Attach | Watch | Print version | History: r11 < r10 < r9 < r8 < r7 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r11 - 2007-10-23 - RichardDonkin
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.