[fpc-devel] https support; call for testers

[Tomas Hajny]

On Fri, May 2, 2014 11:08, Michael Van Canneyt wrote:
> On Fri, 2 May 2014, Tomas Hajny wrote:
>> On Fri, May 2, 2014 08:47, Michael Van Canneyt wrote:
>>> On Thu, 1 May 2014, Tomas Hajny wrote:
>>>
>>>>>
>>>>> I had thought about this. In general, I try to take care of this
>>>>> concern,
>>>>> since it is my concern as well.
>>>>
>>>> What do you mean that you try to take care? Will you try to re-align
>>>> the two and e.g. send the latest improvements to Lukas Gebauer? I'm
>>>> ready to test proper working of my OS/2 support related changes added
>>>> earlier to Synapse once they get merged to the FPC tree. ;-)
>>>
>>> I merged the synapse version to the FPC tree; that took some work.
>>> The FPC tree differs meanwhile too much, it would break existing
>>> code if we just copied over the file.
>>
>> Sure, I understand that just copying the file over isn't the right
>> solution now. If I may suggest, I'd at least mention in comments the
>> Synapse SVN revision to which the synchronization has been performed so
>> that future re-sync efforts may be limited only to differences since the
>> mentioned revision.
>
> Now you are assuming that I know this version :-)

I thought that you had used the Synapse SVN repository
(https://svn.code.sf.net/p/synalist/code/trunk) as your source.


 .
 .
>> Do I understand it correctly that you do not intend to provide the FPC
>> extensions to Lukas Gebauer? I would probably try to do it myself in
>> that
>> case.
>
> They are not so much extensions (although there are a couple, I assume),
> just some cases where things have been done differently.

As far as I can see, there are quite a few additional function imports and
constants added in the FPC version. You can find references to such added
blocks / groups in the "changelog" included in comments at the top (RAND
functions, x509 related declarations); obviously, some sort of graphical
diff & merge tool helps finding the details fairly well.

Tomas