On Thu, Jul 30, 2009 at 11:47 AM, Paul Mossman<[email protected]> wrote: > > Thanks for the EDE feedback Ranga! > > (http://sipx-wiki.calivia.com/index.php/Express_Development_Environment_ > Setup for those who haven't seen it yet.) > > Ranga wrote: >> I am not sure if others have this problem but I thought I >> would state it here: >> I finally made the big leap into FC10. In doing so, I >> decided to try the EDE. I noticed that the EDE was not >> installing some dependencies needed by sipx config such as >> tapestry. > > I think Tapestry pulled in from the sipXconfig jar lib directory in the > source. > (http://sipxecs.sipfoundry.org/rep/sipXecs/main/sipXconfig/lib/) > > >> Our yum repository is still FC8. EDE runs on FC10. >> EDE does not want to update the yum repository information to >> FC8 and hence the RPMs that were to be fetched from sipx >> repsotory were not fetched. > > With the exception of FreeSWITCH, the FC8 RPMs on SIPfoundry actually > work well on FC10, so the EDE does indeed use them. (Look at the > baseurl in /etc/yum.repos.d/sipxecs-unstable-fc.repo, which > ede_build_devuser.sh created for you in Step 4.)
I possibly forgot something fundamental ( gets that way after 1 am. ). I noticed the yum repository descriptor had a define for the fedora version which naturally resolved to 10 on fc 10. I went in there and manually edited it and then it did pull the needful. I do not recall ede_buld_devuser.sh I will try again. > > For the FreeSWITCH RPMs, under FC10 EDE will just build them locally. > > >> If you have all the development >> tools installed, EDE should remove the installed RPMs and >> only install the versions we need for the build. > > The two RPMs you mention this morning were cgicc and > sipx-jasperreports-deps, both of which are SIPfoundry dependency RPMs. > The ede_build_devuser.sh script in Step 4 should always remove and > re-install these RPMs. > > What is the error you encountered? > > Note that the Step 4 ede_build_devuser.sh can be repeatedly re-run, if > you want to try it again. Note though that it causes a fresh re-build, > so all your sipXconfig data and SSL certs will be lost. > > > Thanks. > > > -Paul > [email protected] > > -- M. Ranganathan _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
