On 03/25/2012 04:29 PM, Darrell Anderson wrote:
Seems to me the configure process of both should check for the files and build appropriately on-the-fly.
Yes, but I don't think that would work. Since neither are a dependency of the other a user could choose to install either and for the packager, there is no way to know the user's choice at build time. So it has to be handled from a TDE or packaging standpoint. Preferably from a TDE standpoint. I still think it needs to be a:
(2) drop .protocol files from tdesdk and make tdesvn a dependency of tdesdk.
- or to keep completely independent packages - a proper, but painful
(3) rewrite the tdesdk code to use and install svnsdk+file.protocol, etc..