From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: Adding advisory notification for non-ELPA package.el downloads Date: Tue, 11 Jul 2017 18:57:45 -0400 Message-ID: References: <87h8yk6n1b.fsf@phil.uni-goettingen.de> Reply-To: rms@gnu.org NNTP-Posting-Host: blaine.gmane.org Content-Type: text/plain; charset=Utf-8 X-Trace: blaine.gmane.org 1499814038 1789 195.159.176.226 (11 Jul 2017 23:00:38 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 11 Jul 2017 23:00:38 +0000 (UTC) Cc: cpitclaudel@gmail.com, emacs-devel@gnu.org To: Joost Kremers Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jul 12 01:00:34 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dV48r-0008Oi-1A for ged-emacs-devel@m.gmane.org; Wed, 12 Jul 2017 01:00:29 +0200 Original-Received: from localhost ([::1]:49260 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dV48w-0005rI-GS for ged-emacs-devel@m.gmane.org; Tue, 11 Jul 2017 19:00:34 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39979) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dV46L-00040f-Hg for emacs-devel@gnu.org; Tue, 11 Jul 2017 18:57:54 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dV46K-0003Fq-Lt for emacs-devel@gnu.org; Tue, 11 Jul 2017 18:57:53 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:42456) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dV46E-0003DF-AV; Tue, 11 Jul 2017 18:57:46 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.82) (envelope-from ) id 1dV46D-0002oN-EO; Tue, 11 Jul 2017 18:57:45 -0400 In-reply-to: <87h8yk6n1b.fsf@phil.uni-goettingen.de> (message from Joost Kremers on Mon, 10 Jul 2017 22:43:12 +0200) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:216514 Archived-At: [[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > In itself, it's not a big problem that GNU ELPA uses a different > workflow from MELPA, but, speaking for myself, it would be good if > the ELPA README (or some other document) would contain a few > paragraphs explaining the differences and would cover the steps > involved in such a way that they make sense for someone with a > less-than-stellar understanding of git. I agree. I encourage the people who manage ELPA to do this. > With MELPA, I put my code in a publicly accessible repo > that I create myself, on a service of my own choosing, > and then tell MELPA where to look for it. Is there any reason we should not do this on ELPA? If the repo that ELPA copies from is fully under the control of the developer of that package, I don't see that it matters greatly whether the developer installs changes into that package via ELPA directly, or into some other repo which then gets copied wholesale to ELPA. ELPA managers, does the act of installing directly into ELPA give us an opportunity to make sure something is being handled right? > (in my case Github) If only the developer uses that repo system, we don't have to be concerned with what system it is. But if other contributors are going to be directed to that other repo system, we would want it not to be Github. (See https://gnu.org/software/repo-criteria.html.) -- Dr Richard Stallman President, Free Software Foundation (gnu.org, fsf.org) Internet Hall-of-Famer (internethalloffame.org) Skype: No way! See stallman.org/skype.html.