From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Emanuel Berg Newsgroups: gmane.emacs.devel Subject: Re: Copyright Assignment Date: Tue, 03 Oct 2023 00:18:15 +0200 Message-ID: <87wmw4fz2w.fsf@dataswamp.org> References: <877co5gfm3.fsf@dataswamp.org> <83o7hh6l1u.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="39440"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) To: emacs-devel@gnu.org Cancel-Lock: sha1:xuXiC9s9vP3T9S2xhCXd8zy1658= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Oct 03 07:31:23 2023 Return-path: Envelope-to: ged-emacs-devel@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 1qnY0A-0009wB-Qh for ged-emacs-devel@m.gmane-mx.org; Tue, 03 Oct 2023 07:31:22 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qnXzD-0007Nv-C6; Tue, 03 Oct 2023 01:30:24 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qnRFL-0007Vw-OF for emacs-devel@gnu.org; Mon, 02 Oct 2023 18:18:36 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qnRFJ-0005K4-VK for emacs-devel@gnu.org; Mon, 02 Oct 2023 18:18:35 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1qnRFG-0001lR-NR for emacs-devel@gnu.org; Tue, 03 Oct 2023 00:18:30 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Mail-Copies-To: never Received-SPF: pass client-ip=116.202.254.214; envelope-from=ged-emacs-devel@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Tue, 03 Oct 2023 01:30:21 -0400 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:311248 Archived-At: Eli Zaretskii wrote: >> Good question, I got a mail "Tarball build failure for >> wrap-search" which seems to boil down to >> >> Missing copyright notice in wrap-search/wrap-search.el >> >> Maybe you should just add >> >> ;; Copyright: J Hacker (1997) >> >> to the headers? >> >> I think looking at how other people do it is probably the way >> to find out. Okay, I'm on it ... [...] > > This is all completely unrelated to the OP's request. If I'm allowed to change the subject then, for GNU ELPA one needs ;; Copyright (C) 2023 Free Software Foundation, Inc. as well as ;; This file is part of GNU Emacs. ;; ;; GNU Emacs 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. ;; ;; GNU Emacs 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 GNU Emacs. If not, see . Don't indent that BTW! If you do the folding doesn't work with `elide-head-mode'. Also, after getting the error from GNU ELPA that I reported one should, apart from adding those two things, increment the version number so that ELPA will notice and compile the new version changes. The error message I got in a mail was clear for me to, after several days of not thinking about it, figure out the problem. But it could be more clear, possibly hyperlinking to or even including a boilerplate GNU ELPA package file to show exactly how it should look. I managed to solve it by looking at/in sml-mode.el which I already had from GNU ELPA, but it was a close call, and anywhere below that on the cognitive scale - for me personally, or inside another person - I suppose one would have been completely incomprehensive as to what it was that was suppose to happen. Oh ye humanity! -- underground experts united https://dataswamp.org/~incal