Matching what we use is only relevant for 2 cases.
1) If you want the video functionality to work.  most of the media and codec libs are not packages everywhere and they need to be very recent versions.  Most of what we can do right now in video was not possible 8 months ago.

Luis, if you're finding dependancy problems there's a good chance you don't need all of the modules and can avoid quite a few of the dependancy problems by compiling from source and omitting those modules from the build.

See the modules.conf file (see example build/modules.conf.in - edit and drop it in the same directory as bootstrap.sh named as modules.conf before running bootstrap and configure).

If you can't omit it then you're using the library and if you can't build it against your system version then there's a fair chance your system version is too old to support the feature you're wanting to use, since generally speaking interfaces don't change too much unless features are changing.

On 20 November 2015 at 22:42, Anthony Minessale <anthony.minessale@gmail.com> wrote:


On Thu, Nov 19, 2015 at 5:46 PM, Luis Daniel Lucio Quiroz <luis.daniel.lucio@gmail.com> wrote:

You totally got me wrong.

I was trying to conciliate between the two parts. As someone reclaim the current state of systems. I won't try it again.

And answering your statement. What is your parameter to establish a distribution is still the same?  I was able to build fs16 under centos6. It is still centos6, it was no easy. My productions servers have been running without issues.


You can backpedal if you want but you made a reference to the project being killed for trying to find a stable ongoing platform in Debian among 1000 chaotic distro choices despite the fact that we also still work on a best effort to support every platform.   Naturally when you make statements to cause a whole group of people to think they are wrong for not agreeing with you, they will get annoyed.  You still don't see our point or you would not continue to argue.  Its like we are having a party and you come over to our house and we have some potato chips out with french onion dip and you tell us our party is a dud because we don't have dill dip.  You wan't some dill dip, bring some dill dip.....We'll bring the chips.

 

As far as I remember, the only core lib I updated was alsa, because a module looking for a especific function. All others were new rpm's or updates and They were not part of core  (like glib, dbus, udev just to name examples). Note I am talking about using RPM all time, I don't use  tarballs as I agree with you that doing that breaks any distribution soul.

I disagree when you imply that you must match versions you use. If that would be true, many other big projects would not work. When back porting, You just must match what you need.



Matching what we use is only relevant for 2 cases.

1) If you want the video functionality to work.  most of the media and codec libs are not packages everywhere and they need to be very recent versions.  Most of what we can do right now in video was not possible 8 months ago.

2) You need help.  If a bug ends up related to system lib related issues and it is using a version we are unfamiliar with, then we have to stop there.


 

I agree this is a problem of any 5+ years support distribution; we just have to live with it.

Said this. I think the main topic of discussion was lost.


The main topic is, if you want CentOS to work, help the people who are working on it to get it working.  We supply the build servers and keep an eye on it but we need people who actually care about it to work on doing it right and doing it in a way that will allow things to work on ALL PLATFORMS.  Many build patches for one OS are not sufficient because they break the builds on other platforms.
Its just like code, you need to write code that works in all paths, not just the one you happen to care about.  Keep that in mind and help out and you will have working RPMs.  It has nothing to do with what we prefer or not.


 
Le 19 nov. 2015 5:32 PM, "Anthony Minessale" <anthony.minessale@gmail.com> a écrit :


On Thursday, November 19, 2015, Luis Daniel Lucio Quiroz <luis.daniel.lucio@gmail.com> wrote:

I think this is a big misunderstanding

Brian is right by saying the hard work is done.

But the position the FreeSWITCH project has taken about pushing Debian is a killer for the project.

It is very common that the favor becomes obligation. Specially for those who doesn't understand the open source thinking. But no one can push any one to do things.


I do not appreciate the FUD.   You clearly take for granted the burden of managing a project.  Try to be more considerate.

If you know how to compile code, you can check out git master and go find the tarballs of every dependancy and build, install or make packages of it and it will work.
Our packages are a luxury designed to be used by community members who do not wish to take on the task themselves.  If you do not like them, don't use them.

If you want to make CentOS work the same as Debian, you simply have to manually update all the depends to match the exact versions we use and deal with the cascading dependency yourself.
Once you are done, it will not be CentOS anymore because of all the modifications.  The are behind on libraries because the longer time moves on the harder it is to update all the packages on the distro.
We only have resources for one permutation of this nightmare and with Debian we only have to deal with 2% of the problems CentOS currently has.
If CentOS finally decides to catch up, you will have an easier time getting things to work but that time is not now.







 
Le 19 nov. 2015 12:21 PM, "Brian West" <brian@freeswitch.org> a écrit :
You're highlighting why we have an open source community, its where the community steps up, helps figure this out and contributes the solution to the problem for all to benefit from, Its the least anyone could do thats running FreeSWITCH as the hardest part is already done for you for free! :)

/b


On Thu, Nov 19, 2015 at 5:41 AM, Olgierd Ziolko <lists.fs-users@uce.pw> wrote:
Hi*

But when it's cross-checked against inventory or network drawings he's going to be busted (and put in much worse position).

Personally I find CentOS 7 waaaaaay too edgy for corporate requirements - we (as in my company) are running servers on specific OS version (inc. 6.5, but not 7), custom subset of software, sometimes with custom patches, customised (a whole lot) kernel, so I just can't afford throwing it all out the window just for the sake of using most recent packaged version (and when we're at packages: Debian's packaging is horrendous, how can't such simply systemd service file problem unresolved for months?).

So I'm very on the Andrew's (the first) side.

* hello everyone, I'm kind of fresh FreeSWITCH user and I'll try my best to contribute to the community (because I've already got so much). Thank you all.

On 19 November 2015 at 10:29, Andrew Cassidy <andrew@cassidywebservices.co.uk> wrote:
You can pass PCI-DSS with proper firewall rules. For example, if you FS server only needs to accept calls from certain IP addresses, firewalling it out will pass the automated tests easily.

I know it's not ideal, but I've managed to make unpatched Windows 2003 servers pass the automated tests just by hiding them behind a proxy. 

I'm not condoning this practise, just timelines on that particular project required that they pass until we could upgrade them to Windows 2012. It bought us the time we needed

On 19 November 2015 at 08:21, Andrew Keil <andrew.keil@visytel.com> wrote:

Thanks for your feedback.

 

From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Michael Jerris
Sent: Thursday, 19 November 2015 11:12 AM
To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org>
Subject: Re: [Freeswitch-users] FreeSWITCH version 1.4.x end of life - recommendation please

 

 

On Nov 18, 2015, at 6:49 PM, Andrew Keil <andrew.keil@visytel.com> wrote:

 

To FreeSWITCH users,

 

In order for my client to plan for FreeSWITCH version 1.4.x end of life, I have a few questions that I hope the FreeSWITCH team can help answer:

 

1)      Since the FreeSWITCH version 1.4.x branch is going end of life in early 2016, then obviously I need my client to migrate to the FreeSWITCH version 1.6.x branch ASAP.  Is there a definite date when the FreeSWITCH version 1.4.x branch is going end of life?

 

We don't have a specific date set, we will provide as many critical and security fixes as we can for it for a while.  That being said, we are already at the point where significant portions of fixes are not possible to back-port due to significant changes in the code between 1.4 and 1.6.  This continues to get worse over time.

 

2)      Regarding the FreeSWITCH version 1.6.x branch:

a.       Can this run on CentOS 6.x (ie. the latest release of CentOS 6)?

 

We have made minimal effort to try to package dependencies for it, and it was abandoned as it was determined to be too much work.  Its probably possible, but expect to:

 

1. Not have any support for video features.

2. Spend significant time working on packaging your own dependencies and testing.



 

                                                               i.      I understand that CentOS 7 is recommended, however upgrading the OS is a much bigger task than simply upgrading FreeSWITCH.  Especially since my client is also PCI compliant to enable credit card processing, which requires rigorous Operating System lockdown.  Currently my client will not be using the video features inside FreeSWITCH (ie. initially only using the feature set inside the FreeSWITCH version 1.4.x branch).

                                                             ii.      Is there anything I should be aware of when trying to get FreeSWITCH version 1.6.x branch working on CentOS 6?

 

We have done zero testing on it.  You will have to do all the dependency packaging back-porting for the deps you need and do testing and let us know.



 

I appreciate any feedback that you are able to provide to make this process as painless as possible.

 


_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://confluence.freeswitch.org
http://www.cluecon.com

FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org



--
Andrew Cassidy BSc (Hons) MBCS SSCA

_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://confluence.freeswitch.org
http://www.cluecon.com

FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org


_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://confluence.freeswitch.org
http://www.cluecon.com

FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org



--

Brian West
brian@freeswitch.org


Twitter: @FreeSWITCH , @briankwest
http://www.freeswitchbook.com
http://www.freeswitchcookbook.com

Got Bugs? Report them here! | Reddit: /r/freeswitch

T:+19184209001 | F:+19184209002 | M:+1918424WEST (9378)
iNUM:+883 5100 1420 9001 | ISN:410*543 | Skype:briankwest


_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://confluence.freeswitch.org
http://www.cluecon.com

FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org

_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://confluence.freeswitch.org
http://www.cluecon.com

FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org

_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://confluence.freeswitch.org
http://www.cluecon.com

FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org



--

_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://confluence.freeswitch.org
http://www.cluecon.com

FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org