[Asterisk-bsd] GUI on Freebsd?

[Ian FREISLICH]

Willem Jan Withagen wrote:
> # Fix exec headers
> s|\#\!/usr/bin/php -q|\#\!/usr/bin/env php|;
> s|\#\!/bin/bash|\#\!/bin/sh|;
> 
> # Rewrite the locations of default essential configuration file
> m|/usr/local/| || s|etc/amportal.conf|usr/local/etc/amportal.conf|;
> m|/usr/local/| || s|etc/asterisk|usr/local/etc/asterisk|;
> 
> # Rewite several locations in FreeBSD style
> s|usr/lib/asterisk|usr/local/lib/asterisk|;
> s|var/lib/asterisk|usr/local/share/asterisk|;
> s|var/www/html|usr/local/www/apache22/data|;
> s|var/www|usr/local/www/apache22|;
> s|/html/panel|/data/panel|;
> s|usr/sbin|usr/local/sbin|;

Does this not work sufficiently in ampportal.conf?

ASTETCDIR=/usr/local/etc/asterisk
ASTMODDIR=/usr/local/lib/asterisk/modules
ASTVARLIBDIR=/usr/local/share/asterisk
ASTAGIDIR=/usr/local/share/asterisk/agi-bin
ASTSPOOLDIR=/var/spool/asterisk
ASTRUNDIR=/var/run
ASTLOGDIR=/var/log/asterisk

I think I might have given up in the end and symlinked php5 to
/usr/bin and /usr/local/etc/asterisk to /etc.  Otherwise there's
just too much pain in upgrading with module admin.

> > One of the modules "FreePBX Localization Updates" IIRC uses an
> > incompatible option to cp to install files.  I still need to find
> > the time to make a patch that will work with both Linux and FreeBSD
> > which they will accept.
>
> My current problem is that upgrades again contain all kinds of new
> Linux-isms. So I've made a sort of file fixer that could be run over a
> newly installed package And I saw that cp-problem also, I think while
> trying to load the upgrade of the core framework.

Where I've hit problems that were relatively easy to fix, I've
submitted patches back to FreePBX and they've responded fairly
quickly to those.  I want to solve this cp problem soon because I
have some hardware arriving and when it does, I'm migrating back
to FreeBSD from linux.

See my other post - "Zaptel on FreeBSD-8" for patches to make zaptel
load and work on 8-CURRENT.

> But I posted a similar question on the FreePBX forum, that went
> completely ignored.  So I guess that I'm going to do the same for
> creating the package.

The trouble is that in linux-land "portable" means across linux
strains.

Ian

--
Ian Freislich