From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jean Louis Newsgroups: gmane.emacs.help Subject: Re: NonGNU ELPA (was: Re: Fwd: How do I go about debugging my Elisp code?) Date: Tue, 18 Jan 2022 08:02:26 +0300 Message-ID: References: <87czku1hon.fsf@gnu.org> <87sftpx5ja.fsf_-_@zoho.eu> <874k63auq8.fsf@zoho.eu> <87zgnt7vz5.fsf@zoho.eu> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="10907"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/2.1.5+104 (cd3a5c8) (2022-01-09) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Tue Jan 18 06:07:01 2022 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n9ghx-0002gZ-Al for geh-help-gnu-emacs@m.gmane-mx.org; Tue, 18 Jan 2022 06:07:01 +0100 Original-Received: from localhost ([::1]:43278 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n9ghv-0005CS-MM for geh-help-gnu-emacs@m.gmane-mx.org; Tue, 18 Jan 2022 00:06:59 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:50110) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n9gg9-0003zs-R1 for help-gnu-emacs@gnu.org; Tue, 18 Jan 2022 00:05:12 -0500 Original-Received: from stw1.rcdrun.com ([217.170.207.13]:50611) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n9gg7-0000rs-KU for help-gnu-emacs@gnu.org; Tue, 18 Jan 2022 00:05:09 -0500 Original-Received: from localhost ([::ffff:41.210.155.91]) (AUTH: PLAIN admin, TLS: TLS1.3,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by stw1.rcdrun.com with ESMTPSA id 0000000000037FF5.0000000061E64A7E.00000BA4; Mon, 17 Jan 2022 22:05:02 -0700 Mail-Followup-To: help-gnu-emacs@gnu.org Content-Disposition: inline In-Reply-To: <87zgnt7vz5.fsf@zoho.eu> Received-SPF: pass client-ip=217.170.207.13; envelope-from=bugs@gnu.support; helo=stw1.rcdrun.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:135414 Archived-At: * Emanuel Berg via Users list for the GNU Emacs text editor [2022-01-18 03:11]: > > ;; Copyright (C) 2021 by Emanuel Berg (incal) > > Yeah, but you don't need that, just the licence, right? You need it. It should be known who has copyrights assigned, who is author, and by which license it is published. > I can add a Change Log when there are changes, if they are big > but I don't think that'll happen. Besides should you really > hard-code that, isn't that what you have repositories, VCSs, > etc, for? From: (info "(elisp) Library Headers") ‘;;; Change Log:’ This begins an optional log of changes to the file over time. Don’t put too much information in this section—it is better to keep the detailed logs in a version control system (as Emacs does) or in a separate ‘ChangeLog’ file. ‘History’ is an alternative to ‘Change Log’. > > ;; This file is not part of GNU Emacs. > > > > ;; This program is free software: you can redistribute it and/or > > ;; modify it under the terms of the GNU General Public License as > > ;; published by the Free Software Foundation, either version 3 of the > > ;; License, or (at your option) any later version. > > ;; > > ;; This program is distributed in the hope that it will be useful, but > > ;; WITHOUT ANY WARRANTY; without even the implied warranty of > > ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU > > ;; General Public License for more details. > > ;; > > ;; You should have received a copy of the GNU General Public License > > ;; along with this program. If not, see . > > Again is this an Emacs convention or is it mandatory for > the license? "This file is part or not part of GNU Emacs" is convention. C-h C-c shall tell you how to apply the license. How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. Copyright (C) This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see . Also add information on how to contact you by electronic and paper mail. If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode: Copyright (C) This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an "about box". You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see . That above does not tell you must do it that way. But think about it, you did not put copy of the license with the file. Did you? So I get the file and give it to somebody else, that person, with the header you have where license reference and information about no warranty is missing -- could eventually sue and cause troubles because license was not known and not clearly referenced. A tag like GPL3+ is simply not enough. Don't assume people who receive the program are supposed to know what the tag "GPL3+" means. You cannot even assume that all people have Internet available like you have it. Thus license should be given along the program, see: 4. Conveying Verbatim Copies. You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program. You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee. Emacs is shipped with the license built-in. Rigth? Tag alone is not enough. What if you find a single file in a whole program. Maybe license was included in the package, but now single file goes individually somewhere else. In that case a reference to license would be lost unless it is in the headers. Best way to foster free software with legal notices is already laid out in the GNU GPL 3+ and previous versions. > If it is needed to put the code somewhere (anywhere), I'll be > happy to add it, of course, otherwise I think it is just bulky > and doesn't contribute anything interesting. My code should be > fit for a particular purpose! Still, it's OK to put it like > that, it doesn't change the quality of the code. Mere words ... Legality is important. If there is claim to be "fit for particular purpose" could bring you as author in liabilities. -- Jean Take action in Free Software Foundation campaigns: https://www.fsf.org/campaigns In support of Richard M. Stallman https://stallmansupport.org/