Hi, ----- Il 25-giu-15, alle 19:45, Michael Jerris mike at jerris.com ha scritto: > for things like nasm, is that newer version out there for example in epel? that > would be the best case. Sure, the work I've done is already based on epel, so what is in epel is not built again. I've rebuilt some epel packages only when a newer version is needed. > Backup would be to take a source pacakge from something > newer and just rebuild in a way that doesn't require any modifications, > fallback we can put the src out on our download servers and create a job for > it. As for x264, we will not be putting that in our repo, you'll have to find > some way to get that into some official repo that we can reference, maybe see > if you can get it into epel? The best case would be to get as much as possible > directly into epel so it leaves us having to manage as little as possible. The main "source" of deps (and troubles) is vlc 2.2, which needs a lot of stuff. I've taken some packages from rpmfusion and rebuilt them, updating when needed. So while epel is needed for deps, rpmfusion is not because all needed rpmfusion packages have been rebuilt by me using same sources/specs (if not updated) I don't know if epel will ever accept all packages, because some are also updates to base system, like opencv which is present on CentOS base but too old and ImageMagick, to name few. So the picture is: if you want to have video under CentOS 6 without hosting something (mainly vlc stuff and it's deps), you're out of luck since FS requirements are on very recent packages. Just a quick list of stuff needed: base CentOS updates not present anywhere: ImageMagick (updated), nasm(updated), libvncserver(updated), opencv(updated) ** from rpmfusion: a52dec, faad2, gpac, lame, vlc(updated), libmad, mpg123(updated), x264(updated for vlc 2.2), xvidcore ** from epel (rebuilt because different version) libmpv2(updated), libshout(updated) ** from Freeswitch SD: g722_1, broadvoice, libav, libcodec2, libsilk, libvpx, libyuv(updated), opus, soundtouch, openh264, flite, ilbc (epel has a newer one, pay attention!) This is the list (should be almost complete, I'm not in the office right now) of what I've rebuit to have video running. Is possible to reduce by 6 packages if rpmfusion is added with repo. Dunno if is wanted or not. I think that epel will never accept updates to packages that are already into base distro. And don't know about vlc and its deps... if rpmfusion exists maybe is because patents does not allow it into epel? What do you think? Matteo
On Jun 25, 2015, at 1:45 PM, Michael Jerris <mike@jerris.com> wrote:for things like nasm, is that newer version out there for example in epel? that would be the best case. Backup would be to take a source pacakge from something newer and just rebuild in a way that doesn't require any modifications, fallback we can put the src out on our download servers and create a job for it. As for x264, we will not be putting that in our repo, you'll have to find some way to get that into some official repo that we can reference, maybe see if you can get it into epel? The best case would be to get as much as possible directly into epel so it leaves us having to manage as little as possible.
On Thursday, June 25, 2015, Matteo <mbrancaleoni@voismart.it> wrote:I know how specs works, I'm maintaining a private repo like epel with tens of packages since years, using the same tools used by fedora ( koji, mock, mash).
My intent is not to create a custom build of freeswitch, but a repo like epel or rpmfusion with only the needed build deps.
What is not clear to me is the flow to add a new dep.
Let's say I need to add a bunch of new libs, like gpac, nasm, x264, to name a few.
Which is the correct approach to fit into Fs build structure?
Mat
Inviato da iPhone
> Il giorno 25/giu/2015, alle ore 18:08, Ken Rice ha scritto:
>
> You know in the spec files you can if things for specific versions... You'll
> just have to figure out the correct Ifs for Cent7 vs Cent6 vs say Suse
>
>
>> On 6/25/15, 11:03 AM, "Matteo" wrote:
>>
>> Ok,
>>
>> since some packages are only centos 6 specific updates, how do you plan to
>> handle them?
>>
>> For example, nasm is a required update to CentOS 6 in order to build other
>> stuff,
>> but is not needed for debian or CentOS 7
>>
>> Right now in the repo I don't see anything distro-specific .
>>
>>
>> Regards,
>> Matteo
>>
>> _________________________________________________________________________
>> Professional FreeSWITCH Consulting Services:
>> consulting@freeswitch.org
>> http://www.freeswitchsolutions.com
>>
>> Official FreeSWITCH Sites
>> http://www.freeswitch.org
>> http://wiki.freeswitch.org
>> http://www.cluecon.com
>>
>> FreeSWITCH-dev mailing list
>> FreeSWITCH-dev@lists.freeswitch.org
>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev
>> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev
>> http://www.freeswitch.org
>
> --
> Ken
> http://www.FreeSWITCH.org
> http://www.ClueCon.com
> http://www.OSTAG.org
> irc.freenode.net #freeswitch
> Twitter: @FreeSWITCH
>
>
>
>
> _________________________________________________________________________
> Professional FreeSWITCH Consulting Services:
> consulting@freeswitch.org
> http://www.freeswitchsolutions.com
>
> Official FreeSWITCH Sites
> http://www.freeswitch.org
> http://wiki.freeswitch.org
> http://www.cluecon.com
>
> FreeSWITCH-dev mailing list
> FreeSWITCH-dev@lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev
> http://www.freeswitch.org