Installation English ยป

Installing Froxlor 0.9 on Gentoo Linux

How to get Froxlor into your portage

layman >= 1.3.0

put "http://files.froxlor.org/gentoo/repositories.xml" (without quotes) under "overlays : " in /etc/layman/layman.cfg

1> layman -f && layman -a froxlor

no layman / custom local overlay

1> mkdir -p /usr/local/overlays
2> git clone git://git.froxlor.org/froxlor-gentoo.git /usr/local/overlays/froxlor
3> # if not already added, if you already have a overlay, just add the new one, delimited by a space to the variable in make.conf
4> echo "PORTDIR_OVERLAY=/usr/local/overlays/froxlor" >> /etc/make.conf
5
6> emerge --sync

USE-flags for Froxlor 0.9

The ebuild for Froxlor 0.9 introduces some USE-flags to customize your froxlor-installation:

USE-flag Default value Description
aps Off Enables the Application Packaging Standard
autoresponder Off Enables usage of autoresponder
bind Off Enables support for bind9 nameserver
domainkey Off Enables domain-key entries in domain-zonefiles (requires '+bind')
dovecot Off Enables usage of dovecot mailserver instead of courier
fcgid Off Enables FCGID usage for apache2
ftpquota Off Enables +softquota for proftpd and patches config
fpm Off Enables PHP-FPM usage for webservers
lighttpd Off Use lighttpd-webserver instead of apache2 (USE-flag 'fcgid' will be ignored)
log On Enables the froxlor logging feature (syslog, mysql, file)
mailquota Off Enables usage of mailquota
nginx Off Use nginx-webserver instead of apache2 (USE-flag 'fcgid' will be ignored)
perl Off Enables perl for customers
ssl Off Enables ssl for the froxlor-vhost and customers
tickets On Enables the froxlor ticket support system

If you want to use lighttpd and ssl for example, add the following line to your "/etc/portage/packages.use":

www-apps/froxlor lighttpd ssl

Common problems with emerging Froxlor

In case your one of the fast guys (like me) you'll probably have already tried to

1emerge froxlor

and maybe ran into one or two problems.

Here are the solutions to the most common problems when emerging froxlor:

The 'masked by keyword' - problem

!!! All ebuilds that could satisfy "www-apps/froxlor" have been masked.
!!! One of the following masked packages is required to complete your request:
- www-apps/froxlor-0.9 (masked by: ~x86 keyword)

This is a pretty common error on Gentoo stable systems, because the build requires the KEYWORD ~x86 or ~amd64.

You will need to add www-apps/froxlor to your "/etc/portage/package.keywords":

1echo "www-apps/froxlor" >> /etc/portage/package.keywords

Now you should be able to emerge froxlor without the masked-error.

The 'ssmtp' - problem

[blocks B      ] mail-mta/ssmtp ("virtual/mta" is blocking mail-mta/postfix-2.5.5, mail-mta/ssmtp-2.62-r3)

This one is definetly going to hit most of you guys ;-) But gladly this one can be solved very easy - just remove mail-mta/ssmtp (no fear, postfix will replace the functionality of ssmtp)

1emerge -C mail-mta/ssmtp

The 'wtf? ssmtp still blocks' - problem

Due to a bug in portage, it might happen that you still run into ssmtp-postfix-blocks. If this is the case, just install >=mail-mta/postfix-2.4 prior to froxlor, this should do:

1emerge ">=mail-mta/postfix-2.4"

Finally emerge Froxlor

If you have everything else setup so far, no errors, no blocks, nothing, then you are ready to finally run:

1emerge froxlor

Lean back and relax while your system downloads and compiles the required services for you.

Configure Froxlor using emerge --config

The froxlor-ebuild provides a configure-routine for you. Froxlor and its services will be fully configured after that part.

PLEASE NOTE You have to configure mysql if you haven't done that yet before configuring froxlor

To do so, just run:

1emerge --config =dev-db/mysql-5.x.x

In case you use domainkey you also have to configure dkim-milter prior to froxlor:

1emerge --config dkim-milter

Now you can run the configure script. Just answer all the questions asked and you will be able to start using Froxlor ;-)

1emerge --config www-apps/froxlor