From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: NonGNU ELPA Date: Sat, 21 Nov 2020 19:40:00 -0500 Message-ID: References: <87mtzt6qhf.fsf@gnu.org> <87v9eg4gm5.fsf@gnu.org> <87o8k7yt7n.fsf@gnu.org> <87ima56h1a.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="32581"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Amin Bandali , Richard Stallman , emacs-devel To: Stefan Kangas Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Nov 22 01:41:13 2020 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 1kgdRI-0008Mr-La for ged-emacs-devel@m.gmane-mx.org; Sun, 22 Nov 2020 01:41:12 +0100 Original-Received: from localhost ([::1]:41716 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kgdRH-0007L3-Fx for ged-emacs-devel@m.gmane-mx.org; Sat, 21 Nov 2020 19:41:11 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:55538) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kgdQF-0006ZG-L2 for emacs-devel@gnu.org; Sat, 21 Nov 2020 19:40:07 -0500 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:17079) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kgdQD-0000GY-AY; Sat, 21 Nov 2020 19:40:07 -0500 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 01455440929; Sat, 21 Nov 2020 19:40:03 -0500 (EST) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 5F42B440697; Sat, 21 Nov 2020 19:40:01 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1606005601; bh=2/wMCtamONgtoLsMSV3WIkU4M1HOL08uU7yAQG5AqRM=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=daaeRl/oyW//LdwjfSgJHMPPPLJlgNrZ3IrBrWLuo25Hm3dEXJBqhIMXtaB/WcwfG sEUO93HXqJirrTm4vOLTq5f7CihLoJu87sPKcSAAcvbXu/j1olgPjA2D9ILGN8TpYv 6sRykkvHPrDXQ++SjV1I4ClBuKZE74tqJC7+E9FhYPPG6bxJ2d09n61acrgts53/j/ 6ozvmu2bMVn4ina/DCxi48WxhVc/HU7EfF00E3lRxC+hSDv4ysmthLJm+3Cq6ZAo3U gVhig1jEDR99tvv57t0g3suv1qBTZaiMA9O6JjlAj4E3ZZqDraZCB65RHrxb2WcdB7 Ij+VHGAxI4u7A== Original-Received: from alfajor (69-165-136-52.dsl.teksavvy.com [69.165.136.52]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 18488120337; Sat, 21 Nov 2020 19:40:01 -0500 (EST) In-Reply-To: (Stefan Kangas's message of "Sat, 21 Nov 2020 15:33:21 -0800") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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" Xref: news.gmane.io gmane.emacs.devel:259568 Archived-At: > To build it locally, are the instructions in the README from GNU ELPA > the ones to follow? Yes and no. To build the packages, it's much easier: git clone .../nongnu.git cd nongnu make build/sly or "make build-all" And the result is put into `archive` (as well as `archive-devel` which is what you see in https://elpa.gnu.org/nongnu-devel/ and corresponds to the non-stable Melpa more or less). To "compile the packages in place", you can do "make" and it should work more or less like for elpa.git, but it probably has some rough edges (e.g. a subsequent "make build/sly" might burp because it expects a clean worktree and it might mess with the .gitignore file or something. This part of the code needs to be adapted to the new context). If you feel like taking a shot at the README, that would be welcome ;-) > How easy is it to add a package? Would pushing the attached patch do > the job? It might, but you'll also need to push the code of Magit to the `externals/magit` branch, like in elpa.git. IIUC Magit has various Package-Requires, so you'll have to add those first since we don't want nongnu.git package to require packages only found in Melpa. > Is it useful to start adding packages at this stage? Yes. Stefan