| From: | Matthew J Fletcher |
| Date: | 3 Sep 2000 at 14:19:17 |
| Subject: | Elate Ports & Legal Rubbish (was AMIOPEN: vpcc as a C++ compiler) |
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 ?
I asked before but no responce came, if i remeber the NDA i signed correctly
if i even think about elate in pubilic fleesy will come and beat me up.
regards,
---
Matthew J Fletcher amimjf@connectfree.co.uk
Serck Controls Ltd NPD Firmware
www.amimjf.connectfree.co.uk ICQ amimjf 44193496
Please Use PGP !!! Key Available On Request
Subscribe/Unsubscribe: open-request@amiga.com
Amiga FAQ: http://www.amiga.com/faq.html