| From: | Gary Peake |
| Date: | 4 Sep 2000 at 23:25:02 |
| Subject: | Re: Elate Ports & Legal Rubbish (was AMIOPEN: vpcc as a C++ compiler) |
On Sun, 3 Sep 2000 14:19:17 +0100, owner-open@amiga.com "Matthew J
Fletcher" <amimjf@connectfree.co.uk> wrote:
>Hi,.
>
>> I know about CVS import, but CVS (like RCS and Diff) compares files line
>> by line. So, if just one word changes in a line from 1.12 to 1.13 and I
>> have changed that line already in the Elate port, there is going to be a
>> conflict, which CVS asks me to resolve manually. I don't want that to
>> happen. From Linux, I just unpack the original sources, run ./configure
>> and then elate-post-configure to make the changes (with sed's help).
>
>Of course the best solution would be to get the changes mixed back into
>the orignal port, then you would have none of the above messing around.
>
>Which reminds me, i asked a while ago about the NDA coverage of elates
>internals, if a port needs some elate spesific code (i.e not c cleanups
>or ansi stuff) but say elate threading, can these changes be made public ?
No, our SDK (other than the actual GPL stuff) is proprietary.
Catch the Dream ... Amiga Dream Team