As you might know, LFTP is a popular FTP/SFTP command-line client for most systems. One feature that is lacking from this tool is the ability to do a globbed ls via sftp. I have a patch ready for LFTP that incorporates some of the knowledge [like oddball systems glob() handling] and some of the code from sftp-glob.c for this tool to add this capability. I do, however, have some questions about license issues before I submit the patch to the lftp developers. LFTP is GPL licensed, and openssh is BSD licensed. Is it kosher to incorporate the code into lftp or should I start over from a clean room implementation? Any help is appreciated, -Warren
On Tue, Nov 20, 2007 at 10:37:17AM -0600, warren smith wrote:> LFTP is GPL licensed, and openssh is BSD licensed. Is it kosher to > incorporate the code into lftp or should I start over from a clean > room implementation? > > Any help is appreciated,Thanks for asking! The BSD license that applies to sftp-glob.c permits you to include code in another product, GPL or other license, as long as certain conditions are met. Please see the top of the file sftp-glob.c for the full statement that gives you permission to use, copy modify and distribute the software. //Peter
On Tue, 20 Nov 2007, warren smith wrote:> As you might know, LFTP is a popular FTP/SFTP command-line client for > most systems. One feature that is lacking from this tool is the > ability to do a globbed ls via sftp. I have a patch ready for LFTP > that incorporates some of the knowledge [like oddball systems glob() > handling] and some of the code from sftp-glob.c for this tool to add > this capability. I do, however, have some questions about license > issues before I submit the patch to the lftp developers. LFTP is GPL > licensed, and openssh is BSD licensed. Is it kosher to incorporate the > code into lftp or should I start over from a clean room > implementation?The license (MIT) that the sftp client code is released under does not prohibit incorporation into a GPL project and does not contain any terms that are incompatible with the GPL, so there is no reason to reimplement. You just need to make sure that you follow the terms of the license by preserving the license & copyright notice in whichever files you incorporate code to. -d