2009/11/16 Michael Van Canneyt <[email protected]>: > > > On Mon, 16 Nov 2009, Graeme Geldenhuys wrote: > >> Hi, >> >> We use DCPCrypt in our projects. Compared to the latest download from >> Lazarus CCR site, I have made the following changes. >> >> * Split the one .lpk package into two. One that is runtime only and >> another which is design-time only. This allows DCPCrypt to be used >> with non-LCL based applications - which was previously not possible. >> >> * Simply email a new source archive so it can be made available >> for download from Lazarus CCR on SourceForge
That too. >> >> * Possibly convince somebody to add it as a new package in FCL >> in FPC repository. >> >> * Possibly convince somebody to add it to Lazarus repository like >> what was done with Turbo Power IPPro, AggPas etc.? All these components have in common that they are used or will be used by Lazarus or the LCL itself. >> >> As I stated in a email some months ago. I don't mind maintaining >> DCPCrypt because we use it for our commercial projects. I also don't >> like the idea of *only* having source archives of DCPCrypt like in the >> case of Lazarus CCR downloads, because we can't track any source code >> changes. If it is not added to fpc SVN, I propose to add it to Lazarus CCR svn. >> >> I'm leaning to the idea of having it included in FCL, because it is very >> usable in non-GUI applications as well. In fact, that is how we use it >> currently, in CGI web applications. But I have no say in any of the FPC >> or Lazarus repositories. >> >> >> Any suggestions on what I should do with DCPCrypt and my fixes? > > If DPCrypt's license matches the FCL one, I see no reason not to > include it. Adding to the FCL is the best option. What is the license, Graeme? Vincent -- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
