Hi Andreas, On 09/03/14 02:16, Andreas Tille wrote:
[amul:7] I worked my way through building and testing the encryption libraries until I got it right//. I'm sitting on the DEP-3 headers for all the patches that I created. I hope to upload those soon.[amul:6] TODOs: - CMakeLists.txt for V6.1-000 does not build the encryption libraries. The builds work, but I need to (a) test the result, (b) create the patch for the debian package, (c) carry the build changes forward to the upstream release and lastly, (d) update the source README. - Fix the issue where the /opt/fis-gtm/current link points to the 32bit version of GT.M for the 64bit install - Allow i386 and x86_64 packages to coexist. Currently the packages conflict. Also ensure that users can install multiple GT.M versions. [amul:6] I'm working on the top bullet right now. I will follow up with questions - after searching :) - for the last two.
[amul:7] To manage the default "current" link, /opt/fis-gtm/current, debian/rules includes a override_dh_link target. We would like to let users install GT.M version 6.0-003 and V6.1-000 concurrently. Any ideas on achieving a "current" link without using a postinst/prerm script?
[amul:7] To install both 32bit and 64it versions of GT.M on the same machine, we are considering going with two separate packages or multiarch. What are your thoughts on separate packages vs multiarch? If I read everything correctly, the ia32-libs model is being replaced with multiarch.
thanks, Amul _____________ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.