Re: [racket-dev] Too many license files
Great, I mis-posted that to users not dev. Gah. On Thu, Feb 27, 2014 at 12:12 PM, Greg Hendershott greghendersh...@gmail.com wrote: On Fri, Feb 21, 2014 at 10:51 AM, Matthew Flatt mfl...@cs.utah.edu wrote: Yes, the duplicate files bother me, too. I think removing the duplicates will require yet another little twist in the package system (since the files originate from individual packages), so we've left them for now. At Fri, 21 Feb 2014 11:45:50 -0500, Neil Van Dyke wrote: I'm not a lawyer, but I figured that, for most packages I author, I probably don't *need* to include the full text of a well-known license (e.g., LGPLv3). Instead, I give the copyright notice, state that the license using the recognized full name of the license (and a URL), and then some disclaimers. Speaking of referencing rather than copying licenses, and third party pkgs: It would be helpful for some sort of canonical license ID or URI to be part of the official metadata in info.rkt and on pkgs.racket-lang.org. That way someone could filter packages by license when browsing the pkg web site. Also, it could enable `raco pkg` (or a third-party utility) to do a license compatibility check down the dependency chain. Even just license missing would be helpful to know, transitively. Plus there's license compatibility. (That taxonomy or permissiveness ordinality doesn't necessarily need to be baked into the license URIs; it could come from elsewhere, but use the URIs.) _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] Too many license files
At Fri, 21 Feb 2014 12:17:26 +0100, Togan Muftuoglu wrote: As I am testing upcoming 6.0 release build process, one thing that strikes me is the number of LICENCE.txt files, 166 of them. add the 3 for the copying COPYING-libscheme.txt, COPYING_LESSER.txt, COPYING.txt makes 169 in total. Is is really necessary to have the 166 copies of the same file ? Mind you it is not the size but identical file being installed 166 times is the issue here Yes, the duplicate files bother me, too. I think removing the duplicates will require yet another little twist in the package system (since the files originate from individual packages), so we've left them for now. _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] Too many license files
For at least third-party packages (though you might want something trickier for core Racket)... I'm not a lawyer, but I figured that, for most packages I author, I probably don't *need* to include the full text of a well-known license (e.g., LGPLv3). Instead, I give the copyright notice, state that the license using the recognized full name of the license (and a URL), and then some disclaimers. I include this legal info in metadata in info.rkt, and McFly makes it appear automatically in the documentation (with, e.g., LGPLv3 at the top of the document, and the free-form legal blurb at the end of the document). Example at: http://www.neilvandyke.org/racket-roomba/ I've started to also add a one-line copyright notice at the top of each source file in the package, something like ;; Copyright Neil Van Dyke. See file info.rkt. (I might have to move to a legal notice comment block at the top of each file, but I'd really rather not. Notice blocks don't seem to be a barrier to abuse anyway.) Neil V. _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] Too many license files
That sounds much more sensible than including COPYING.txt and COPYING_LESSER.txt everywhere. Unless someone tells me that it's a bad idea, I'll switch packages to refer to LGPL by reference. At Fri, 21 Feb 2014 11:45:50 -0500, Neil Van Dyke wrote: For at least third-party packages (though you might want something trickier for core Racket)... I'm not a lawyer, but I figured that, for most packages I author, I probably don't *need* to include the full text of a well-known license (e.g., LGPLv3). Instead, I give the copyright notice, state that the license using the recognized full name of the license (and a URL), and then some disclaimers. I include this legal info in metadata in info.rkt, and McFly makes it appear automatically in the documentation (with, e.g., LGPLv3 at the top of the document, and the free-form legal blurb at the end of the document). Example at: http://www.neilvandyke.org/racket-roomba/ I've started to also add a one-line copyright notice at the top of each source file in the package, something like ;; Copyright Neil Van Dyke. See file info.rkt. (I might have to move to a legal notice comment block at the top of each file, but I'd really rather not. Notice blocks don't seem to be a barrier to abuse anyway.) Neil V. _ Racket Developers list: http://lists.racket-lang.org/dev _ Racket Developers list: http://lists.racket-lang.org/dev
