On 2017/01/04 08:42 PM, deloptes wrote:
> 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.
Slavek and I have our own scripts to automate building TDE.
About 3 years ago we had some discussions about releasing these scripts after R14.0.0 was out, then for a reason or
another we kept procrastinating :-(
Your email is a good reminder that we need to do something here!
I will need to do some changes to my scripts to be able to add them to our GIT packaging repo. Will you be willing to
test them out (together of course) when they are ready? If so, I will make a point of doing this extra effort after
Slavek and I complete the openssl migration.