Jonas Karlsson wrote: > On Mon, 26 Nov 2007 20:38:47 +0100, Giambattista Bloisi <[EMAIL PROTECTED]> > wrote: > > >> Hisham Muhammad wrote: >> >>> On Nov 26, 2007 5:08 PM, Carlo Calica <[EMAIL PROTECTED]> wrote: >>> >>> >>>> On 11/24/07, Giambattista Bloisi <[EMAIL PROTECTED]> wrote: >>>> >>>> >>>>> Hi all, >>>>> I'm working on recipes for KDE 4. I installed it successfully on my >>>>> system anyway before submitting Recipes I'm concerned about a few issues >>>>> I found. >>>>> >>>>> The first problem is that KDE 4 is based on cmake. AFAIK at the moment >>>>> only cvs version of Compile supports cmake. Is it ok to to post recipes >>>>> that require cvs versions of Compile ? >>>>> >>>>> >>>>> >>>> I would say that they don't belong in the official store but post them >>>> for interested individuals. >>>> >>>> >>> And I would say it's about time I make a new Compile release. So, is >>> cmake support in Compile stable/complete enough? Did you have to make >>> any ugly workarounds to build KDE, etc.? If improvements are needed, I >>> would be happy to implement them before a release that affects the >>> Compile recipes specification. >>> >>> >>> >> cmake works fine. When I worked on KDE 3.95.0 I had to change it >> (support for need_build_directory=no) to compile KDE-Support: but as of >> today I can compile it using the official version. I think it no longer >> requires to be built in the distribution dir. >> I should check again all my KDE recipes: unfortunately this takes a lot >> of time! >> >> > CMake should not require to be built in the source dir. On the contrary > projects are supposed to be built outside of the source directory. What > were the issues you were experiancing with KDE4 and a separate build > directory? > > My issue was that I was unable to build KDE-support inside the build dir used by Compile, but only in the source dir (../). I don't have this isse any more. So I don't think it worth spending time on it. I'm now trying to compile KDE without KDE-support.
>>>>> KDE 4 also requires a package named "KDE-Support" which is available >>>>> only using svn. Therefore in the Dependencies file I see an entry like >>>>> "KDE-Support 20071115-SVN". Is that ok as well ? >>>>> KDE-Support required me to recompile svn since the one shipped with the >>>>> binary package did not support https protocol. I had a similar problem >>>>> with rpm and OpenOffice where I had to recompile rpm beacuse it was not >>>>> able to handle the rpms of OpenOffice. >>>>> >>>>> >>>>> >>>> Is there a reason svn doesn't support https? What are the extra deps >>>> to support it? Without a reason to avoid https support, I'd like it >>>> in the official recipe.รน >>>> >>>> >>> It should support http... Giambattista, did you have to change the >>> dependencies and/or flags? Let me know if the latest recipe is okay >>> and I'll rebuild the binary package. >>> >>> >>> >> I just did a "Compile svn" and after that it worked. The same for rpm. >> > > It may have to do with how Neon is built. Neon is the library svn uses for > http(s) access and it has happened before that Neon was built without https > support. > > Another idea I had was about openssl. I noticed that upgrading openssl causes NTPD not to work as it checks that openssl matches the version against it was compiled. Do you know whether is possible to mark this type of dependecy inside a recipe ? >>>> Thanks for taking the initiative on this! >>>> >>>> >>> Seconded! >>> >>> > Thirded (or something :) ) > > _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
