Michele Calgaro wrote: > You need to download the latest sources, then rebuild everything up to > tdelibs and tdebase. Let me know if you are using R14.1.x, in that case it > is necessary to disable pkcs support in tdelibs for the time being, since > we haven't fixed that yet. Also expects some other packages to still > FTBFS, we are still working on the issue. > Hi, thanks to both of you. I started now building tdelibs. My base is debian jessie and some or most of the packages I rebuild from git. We'll see if something fails. I was wondering if you can help me getting a proper build environment, where I can rebuild locally dependent packages. For now I have all on my local drive, but I would prefer to move it on my server and have access via nfs. The question is if you have best practice recommendation on this and if there is a common way to automate git update and build ... I don't want to have more than needed for testing. Ideally I have all the packages I need in a TDE directory, but I found out that I must maintain a file with dependences if I want to automagically build all I want to test, so I was thinking I write a script where I provide the arguments in the build order I want: tdelibs tdebase in this case? I am sure you have been thinking about this already. thanks --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-devel-unsubscribe@xxxxxxxxxxxxxxxxxxxxxxxxxx For additional commands, e-mail: trinity-devel-help@xxxxxxxxxxxxxxxxxxxxxxxxxx Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
