<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Possibly a bit unfair to say, it can be a matter of discoverability.<br>
<br>
To explain what I do when searching for software to meet my needs.<br>
<br>
I will first look for software in distribution specific resources,
including the package manager and distribution's wiki. If there is
something mentioned there then it most likely is going to be the
simplest and quickest option to get it running (the package manager
should do all the dependency checks, get the require dependencies
and configure the system), distribution documentation is most likely
to discuss software which works well under that distribution or
comment on specific things which need doing on that distribution.<br>
<br>
If at this point I have found something which meets my needs then I
need not look further. However should I not be satisfied with the
options at this point I will of course look further.<br>
<br>
Also I will read documentation, search the internet for solutions to
problems, etc.<br>
<br>
My point being though, I might not find software which is not in a
official distribution if something which can do the job is in the
official distribution. This is not because I am being lazy but
rather I want to use my time efficiently, I prefer to use software
than search for it.<br>
<br>
Michael Whapples<br>
<div class="moz-cite-prefix">On 16/03/2013 20:12, Avi Marcus wrote:<br>
</div>
<blockquote
cite="mid:%3CCALNZuwmCKi6F2ks-dCpT_vPz1wyncU-eL6R9nNBaW_1BfL_-Kg@mail.gmail.com%3E"
type="cite">
<div dir="ltr">If that's what's stopping them from trying FS,
especially if there is a .deb ready and waiting, then I expect
the community will have to answer a LOT of very basic questions
from them that are already answered on ML / wiki / book...
<div>
<div><br>
</div>
<div>
<div>
<div dir="ltr"><span
style="font-family:Verdana,Arial,Helvetica,sans-serif;font-size:small">-Avi<br>
</span></div>
</div>
<br>
<br>
<div class="gmail_quote">On Sat, Mar 16, 2013 at 10:37 PM,
Ken Rice <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:krice@freeswitch.org" target="_blank">krice@freeswitch.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<font face="Monaco, Courier New"><span
style="font-size:11pt">Getting it into official
repos only helps gain wider adaption, many people
wont even try something if they cant just type
${package_manager} install ${application}
<div class="im">
<br>
<br>
<br>
<br>
On 3/16/13 12:55 PM, "Avi Marcus" <<a
moz-do-not-send="true"
href="http://avi@avimarcus.net"
target="_blank">avi@avimarcus.net</a>>
wrote:<br>
<br>
</div>
</span></font>
<blockquote>
<div class="im"><font face="Monaco, Courier New"><span
style="font-size:11pt">At the speed that FS
updates, I don't particularly see the point of
getting it into the official repos...<br>
<br>
-Avi<br>
<br>
<br>
On Sat, Mar 16, 2013 at 8:47 PM, Cal Leeming
[Simplicity Media Ltd] <<a
moz-do-not-send="true"
href="http://cal.leeming@simplicitymedialtd.co.uk"
target="_blank">cal.leeming@simplicitymedialtd.co.uk</a>>
wrote:<br>
</span></font></div>
<blockquote>
<div class="im"><font face="Monaco, Courier New"><span
style="font-size:11pt"><br>
<br>
On Sat, Mar 16, 2013 at 7:16 PM, Ken Rice
<<a moz-do-not-send="true"
href="http://krice@freeswitch.org"
target="_blank">krice@freeswitch.org</a>>
wrote:<br>
</span></font>
<blockquote><font face="Monaco, Courier New"><span
style="font-size:11pt">So that’s 1 for
10AM Eastern (CDT) or 2PM GMT Wed.<br>
<br>
The problem with installing all the
modules is that you don’t always need or
want them installed on the system. And
there are a huge number of people doing
embedded work with FreeSWITCH. Take Apache
as another example a quit apt-cache search
apache2 shows dozens of apache2
packagesthat you must install to get that
functionality after the fact.<br>
</span></font></blockquote>
<font face="Monaco, Courier New"><span
style="font-size:11pt"><br>
Actually you do have a good point here.<br>
<br>
$ apt-cache search apache2 | grep apache |
wc -l<br>
97<br>
<br>
</span></font>
<blockquote><font face="Monaco, Courier New"><span
style="font-size:11pt"><br>
The whole point of meta packages or config
packages for FreeSWITCH is to try and keep
this consistant across all platforms be it
RHEL/Centos or Debian or even Ubuntu. This
reduces the amount of bandwidth required
to supporting the various things after FS
has been installed.<br>
<br>
Personally if it were up to me I would say
screw all the different variations between
how FHS and other file layouts work and
say pick one of the following,
/opt/freeswitch or /usr/local/freeswitch
we are going to install everything in
those locations. This would drastically
reduce support issues and greatly improve
the ability of users to backup and change
things in FS w/out having to search the
entire filesystem to figure out where
something as simple as
freeswitch/db/zrtp.dat is located.<br>
</span></font></blockquote>
<font face="Monaco, Courier New"><span
style="font-size:11pt"><br>
In Debian packaging etiquette (afaik), /opt/
is used usually for non-free packages, or
packages where the source code is not given
out and moving files around would break the
pre-compiled binary. If the end goal was to
get FS included in the Debian mirrors, then
you'd need to go beyond just
/usr/local/freeswitch.. it'd have to be
split into /etc/freeswitch,
/var/log/freeswitch etc.<br>
<br>
</span></font>
<blockquote><font face="Monaco, Courier New"><span
style="font-size:11pt"><br>
Yes I know that last statement will cause
a ton of arguments with people as getting
started on where things should go on a
file system layout is as toxic as starting
a debat on religion or politics, but
that’s not the point, we are not a
distribution, we are a project developing
a specific software package. That being
said I honestly believe the single install
location is the proper thing to do, but we
can have support for FHS install locations
etc in the build/packaging scripts to ease
distro packagers lives for getting
packages into the main distro repo’s. But
even then we will still have to maintain
packages for FreeSWITCH proper repos as
you already know how hard it is to get the
latest release of software for many thing
(for crying out loud, centos still ships
Postgresql 8, and they are up to 9.2.3)<br>
</span></font></blockquote>
<font face="Monaco, Courier New"><span
style="font-size:11pt"><br>
It really depends what the agreed end goal
is.<br>
<br>
If we want to one day have it in the various
OS mirrors, then it'll have to be done
properly. This will increase complexity, and
end up with more time needing to be spent.
Packaging is a skill/art in its own rights,
and you'd need dedicated people to work on
packaging for the various OS's. Personally,
I think the only benefit for splitting up
the layout would be if you want to get it
included in the official OS mirrors. However
if this is not the case, then having it all
inside a single directory is going to be
quicker and easier, leaving people with more
time to focus on other things.<br>
<br>
If having it under a single dir is agreed,
according to [3], /etc/opt is expected to
store configuration files related to
packages inside /opt, the use of /usr/local
[1] and /opt [2] appears to be OS specific
[4]. I don't have any strong opinions of
whether it should be /opt or /usr/local.<br>
<br>
[1] /usr/local - <a moz-do-not-send="true"
href="http://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard#cite_note-29"
target="_blank">http://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard#cite_note-29</a><br>
[2] /opt - <a moz-do-not-send="true"
href="http://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard#cite_note-.2Fopt-27"
target="_blank">http://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard#cite_note-.2Fopt-27</a><br>
[3] <a moz-do-not-send="true"
href="http://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard"
target="_blank">http://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard</a><br>
[4] <a moz-do-not-send="true"
href="http://stackoverflow.com/questions/12649355/what-does-opt-mean-as-in-the-opt-directory-is-it-an-abbreviation"
target="_blank">http://stackoverflow.com/questions/12649355/what-does-opt-mean-as-in-the-opt-directory-is-it-an-abbreviation</a><br>
<br>
</span></font></div>
<blockquote><font face="Monaco, Courier New"><span
style="font-size:11pt"><br>
K
<div class="im"><br>
<br>
<br>
<br>
On 3/16/13 11:14 AM, "Cal Leeming
[Simplicity Media Ltd]" <<a
moz-do-not-send="true"
href="http://cal.leeming@simplicitymedialtd.co.uk"
target="_blank">cal.leeming@simplicitymedialtd.co.uk</a>
<<a moz-do-not-send="true"
href="http://cal.leeming@simplicitymedialtd.co.uk"
target="_blank">http://cal.leeming@simplicitymedialtd.co.uk</a>>
> wrote:<br>
<br>
</div>
</span></font>
<blockquote><font face="Monaco, Courier New"><span
style="font-size:11pt">
<div class="im">Sure I'm up for that,
though I think discussing a bit more on
email before hand would be a good idea
too.<br>
<br>
I can do 10am Eastern on Wednesday,
which would be 2pm GMT/UK time for us.<br>
<br>
To clarify my own position on
packaging.. Having the packages split
into their individual modules is a nice
idea in theory, but it doesn't feel like
the 'Debian way'. Most Debian users are
used to only installing just a few
packages, and the package maintainer
decides what should be compiled in by
default (take nginx for example). The
application then decides which modules
should be loaded in using the .so files
(for example Apache). The exception to
this is Python, where you have external
Python modules (such as python-curl),
however these not part of the Python
core, thus why they are kept separate.
Standard python modules (such as zlib)
are all included by default.<br>
<br>
I don't know enough about how FreeSWITCH
module linking works, but I would have
thought that if a module is compiled
dynamically, then it won't be linked in
unless it's specified in
modules.conf.xml. In which case, you
could just have a single package with
all the dynamic modules compiled in, and
you would change which modules are
loaded in by editing your
modules.conf.xml. On that basis, I think
that the modules should be compiled as a
single package.<br>
<br>
Any thoughts?<br>
<br>
Cal<br>
<br>
</div>
<div class="im">
On Sat, Mar 16, 2013 at 5:18 PM, Ken
Rice <<a moz-do-not-send="true"
href="http://krice@freeswitch.org"
target="_blank">krice@freeswitch.org</a>
<<a moz-do-not-send="true"
href="http://krice@freeswitch.org"
target="_blank">http://krice@freeswitch.org</a>>
> wrote:<br>
</div>
</span></font>
<blockquote><font face="Monaco, Courier New"><span
style="font-size:11pt">
<div class="im">Debian Packages... Why
don’t you guys all get together on the
FS conf bridge, and lets get everyone
working together to get these done in
a common way... Hows Say Noon Eastern
on Tuesday for 10 Eastern on Wed (an
hour before the regular weekly call)
to get all you guys in 1 bridge to
nail this down.<br>
<br>
<br>
<br>
</div>
<div class="im">
On 3/15/13 6:21 PM, "Anthony
Minessale" <<a
moz-do-not-send="true"
href="http://anthony.minessale@gmail.com"
target="_blank">anthony.minessale@gmail.com</a>
<<a moz-do-not-send="true"
href="http://anthony.minessale@gmail.com"
target="_blank">http://anthony.minessale@gmail.com</a>>
<<a moz-do-not-send="true"
href="http://anthony.minessale@gmail.com"
target="_blank">http://anthony.minessale@gmail.com</a>>
> wrote:<br>
<br>
</div>
</span></font>
<blockquote><font face="Monaco, Courier New"><span
style="font-size:11pt">
<div class="im">Work with ken and we
can combine forces and release
packages too.<br>
<br>
</div>
<div class="im">
On Mar 15, 2013 6:29 PM, "Andrew
Cassidy" <<a
moz-do-not-send="true"
href="http://andrew@cassidywebservices.co.uk"
target="_blank">andrew@cassidywebservices.co.uk</a>
<<a moz-do-not-send="true"
href="http://andrew@cassidywebservices.co.uk"
target="_blank">http://andrew@cassidywebservices.co.uk</a>>
<<a moz-do-not-send="true"
href="http://andrew@cassidywebservices.co.uk"
target="_blank">http://andrew@cassidywebservices.co.uk</a>>
> wrote:<br>
</div>
</span></font>
<blockquote><font face="Monaco, Courier
New"><span style="font-size:11pt">
<div class="im">I just wrote a
script that chroots and builds for
each env I have installed using
the provided build scripts.<br>
<br>
</div>
<div>
<div class="h5">
On 15 March 2013 20:27, Cal
Leeming [Simplicity Media Ltd]
<<a moz-do-not-send="true"
href="http://cal.leeming@simplicitymedialtd.co.uk"
target="_blank">cal.leeming@simplicitymedialtd.co.uk</a>
<<a moz-do-not-send="true"
href="http://cal.leeming@simplicitymedialtd.co.uk"
target="_blank">http://cal.leeming@simplicitymedialtd.co.uk</a>>
<<a moz-do-not-send="true"
href="http://cal.leeming@simplicitymedialtd.co.uk"
target="_blank">http://cal.leeming@simplicitymedialtd.co.uk</a>>
> wrote:<br>
</div>
</div>
</span></font></blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<font face="Monaco, Courier New"><span
style="font-size:11pt">
<div>
<div class="h5">Hello,<br>
<br>
I've recently released an alternative Debian
package builder for FreeSWITCH.<br>
<br>
<a moz-do-not-send="true"
href="https://github.com/foxx/freeswitch-debian"
target="_blank">https://github.com/foxx/freeswitch-debian</a><br>
<br>
Although FreeSWITCH does already have suitable
Debian packages (and a builder), it might not
be suitable for your needs (and in our
specific use case, we required an alternative
approach).<br>
<br>
Some of the reasons for this might be;<br>
<br>
* Build your own packages with custom patches
applied<br>
* Your build system requires an easy to use, 1
command buider<br>
* Building your own source packages from GIT
for security reasons<br>
* Have a single Debian package to install
rather than 100+<br>
<br>
It supports the following features;<br>
<br>
* Uses 'get-packaged-orig-source' to fetch
original source from FreeSWITCH git<br>
* Builds as non-native, all arch package using
quilt 3.0 patching (in accordance with Debian
guidelines)<br>
* Uses start-stop-daemon<br>
* Uses pbuilder to ensure a clean build<br>
* Creates 'freeswitch' system user and
enforces permissions on FreeSWITCH files<br>
* Installs into /opt/freeswitch, rather than
system dirs<br>
* Removing/purging package will NOT remove
data/logs dir or delete 'freeswitch' system
user (in accordance with Debian guidelines)<br>
* Enforces all necessary dependancies<br>
<br>
Usage:<br>
<br>
# Replace GIT_REF with the ref from GIT you
wish to compile against<br>
# Replace FS_VERSION with the version of
FreeSWITCH we are compiling<br>
<br>
$ apt-get install git<br>
$ git clone <a moz-do-not-send="true"
href="https://github.com/foxx/freeswitch-debian.git"
target="_blank">https://github.com/foxx/freeswitch-debian.git</a><br>
$ cd freeswitch-debian<br>
$ GIT_REF=master FS_VERSION=1.3.16 make<br>
<br>
Hope this helps someone else!<br>
<font color="#888888"><br>
Cal<br>
</font><br>
_________________________________________________________________________<br>
Professional FreeSWITCH Consulting Services:<br>
</div>
</div>
<a moz-do-not-send="true"
href="http://consulting@freeswitch.org"
target="_blank">consulting@freeswitch.org</a>
<<a moz-do-not-send="true"
href="http://consulting@freeswitch.org"
target="_blank">http://consulting@freeswitch.org</a>>
<<a moz-do-not-send="true"
href="http://consulting@freeswitch.org"
target="_blank">http://consulting@freeswitch.org</a>>
<br>
<div class="im">
<a moz-do-not-send="true"
href="http://www.freeswitchsolutions.com"
target="_blank">http://www.freeswitchsolutions.com</a><br>
<br>
FreeSWITCH-powered IP PBX: The CudaTel
Communication Server<br>
<a moz-do-not-send="true"
href="http://www.cudatel.com" target="_blank">http://www.cudatel.com</a><br>
<br>
Official FreeSWITCH Sites<br>
<a moz-do-not-send="true"
href="http://www.freeswitch.org"
target="_blank">http://www.freeswitch.org</a><br>
<a moz-do-not-send="true"
href="http://wiki.freeswitch.org"
target="_blank">http://wiki.freeswitch.org</a><br>
<a moz-do-not-send="true"
href="http://www.cluecon.com" target="_blank">http://www.cluecon.com</a><br>
<br>
FreeSWITCH-users mailing list<br>
</div>
<a moz-do-not-send="true"
href="http://FreeSWITCH-users@lists.freeswitch.org"
target="_blank">FreeSWITCH-users@lists.freeswitch.org</a>
<<a moz-do-not-send="true"
href="http://FreeSWITCH-users@lists.freeswitch.org"
target="_blank">http://FreeSWITCH-users@lists.freeswitch.org</a>>
<<a moz-do-not-send="true"
href="http://FreeSWITCH-users@lists.freeswitch.org"
target="_blank">http://FreeSWITCH-users@lists.freeswitch.org</a>>
<br>
<div class="im">
<a moz-do-not-send="true"
href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users"
target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a moz-do-not-send="true"
href="http://lists.freeswitch.org/mailman/options/freeswitch-users"
target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a moz-do-not-send="true"
href="http://www.freeswitch.org"
target="_blank">http://www.freeswitch.org</a><br>
<br>
</div>
</span></font>
<div class="im">
<blockquote>
<blockquote>
<blockquote>
<blockquote>
<blockquote>
<blockquote>
<blockquote><font face="Monaco, Courier
New"><span style="font-size:11pt"><br>
<br>
</span></font></blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<font face="Monaco, Courier New"><span
style="font-size:11pt"><br>
-- <br>
Ken<br>
<font color="#0000FF"><u><a
moz-do-not-send="true"
href="http://www.FreeSWITCH.org"
target="_blank">http://www.FreeSWITCH.org</a><br>
<a moz-do-not-send="true"
href="http://www.ClueCon.com"
target="_blank">http://www.ClueCon.com</a><br>
<a moz-do-not-send="true"
href="http://www.OSTAG.org"
target="_blank">http://www.OSTAG.org</a><br>
</u></font><a moz-do-not-send="true"
href="http://irc.freenode.net" target="_blank">irc.freenode.net</a>
#freeswitch<br>
</span></font>
</div>
</div>
<br>
_________________________________________________________________________<br>
Professional FreeSWITCH Consulting Services:<br>
<a moz-do-not-send="true"
href="mailto:consulting@freeswitch.org">consulting@freeswitch.org</a><br>
<a moz-do-not-send="true"
href="http://www.freeswitchsolutions.com"
target="_blank">http://www.freeswitchsolutions.com</a><br>
<br>
FreeSWITCH-powered IP PBX: The CudaTel Communication
Server<br>
<a moz-do-not-send="true" href="http://www.cudatel.com"
target="_blank">http://www.cudatel.com</a><br>
<br>
Official FreeSWITCH Sites<br>
<a moz-do-not-send="true"
href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<a moz-do-not-send="true"
href="http://wiki.freeswitch.org" target="_blank">http://wiki.freeswitch.org</a><br>
<a moz-do-not-send="true" href="http://www.cluecon.com"
target="_blank">http://www.cluecon.com</a><br>
<br>
FreeSWITCH-users mailing list<br>
<a moz-do-not-send="true"
href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a moz-do-not-send="true"
href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users"
target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a moz-do-not-send="true"
href="http://lists.freeswitch.org/mailman/options/freeswitch-users"
target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a moz-do-not-send="true"
href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>