From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Andrea Corallo Newsgroups: gmane.emacs.devel Subject: Re: having emacs-matlab in ELPA, finally. FSF paper signed Date: Wed, 07 Aug 2024 13:54:15 -0400 Message-ID: References: <871q37um8q.fsf@mat.ucm.es> <87v80cp8nx.fsf@mat.ucm.es> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="37874"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: To: Uwe Brauer Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Aug 07 19:55:01 2024 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 1sbksH-0009cp-CR for ged-emacs-devel@m.gmane-mx.org; Wed, 07 Aug 2024 19:55:01 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sbkrb-0002R7-OO; Wed, 07 Aug 2024 13:54:19 -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 1sbkrY-0002Eq-Cu for emacs-devel@gnu.org; Wed, 07 Aug 2024 13:54:16 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sbkrX-00016a-KO; Wed, 07 Aug 2024 13:54:15 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-Version:Date:References:In-Reply-To:Subject:To: From; bh=wjhM7froWEJtApN6TOMBP6fNQxylVQjgbNCYbTRQvhY=; b=avzR+CyaqjDuCKZj3yZA /KDG+5sxHPKfKsZlBmhdoTCz3UOkvyCBtf1H5v4ehLLKOlc/qVMMs8q+UxGrnqsyWNwzhicwhtJmm gQiyEnXWeJVElDIC/86XWHhNc3B3PWwqLTg9542pDQib1sfkYtvqaMdJD+2ayBRzf++kwCoOgAs72 o1+M6aiLM52WX5ux4g09H1tfi9AOp1MMkwq2qIjw8G89u9W2R6djjdhXQFfhBp6xGe/Gxj+6nlP3f /aGOmgzcw2dKtB3IjZsvHM/goBjY28eiOUzuJ64Zgt0bhYR5bcDy/XJxcp8y7tLEYg8NlPyuGOXCJ HPRMV+aEg9NxbQ==; Original-Received: from acorallo by fencepost.gnu.org with local (Exim 4.90_1) (envelope-from ) id 1sbkrX-0000dD-DL; Wed, 07 Aug 2024 13:54:15 -0400 In-Reply-To: <87v80cp8nx.fsf@mat.ucm.es> (Uwe Brauer's message of "Wed, 07 Aug 2024 19:03:30 +0200") 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:322515 Archived-At: Uwe Brauer writes: >>>> "AC" =3D=3D Andrea Corallo writes: > >> Uwe Brauer writes: >>> Hi all >>>=20 >>> After quite a bit of time I can say the following : >>>=20 >>> 1) All authors/contributors have either signed the corresponding FSF >>> papers, in the very few cases where they have not, their >>> corresponding code has been completely removed and therefore >>> matlab-emacs could be in ELPA. Eli gave me his ok. (And RMS a >>> while ago, if all legal requirements would be satisfied, of course). > >> Hi, > >> that's great news! > >>> 2) Can someone please provide me with some information or a link how >>> to proceed? I have to say that we, the authors, are now cleaning >>> up a bit the repository, rebase, delete obselete branches etc, >>> before including the package in ELPA. > >> The ELPA README is the place to start from >> > > Thanks for this pointer. I had a first glance, it reminds me very much > on the xemacs package system (but that used mercurial not git=F0=9F=98=89= ).=20 > > I have to read it in more details, but so far, I have two questions. > > 1. The name of the branches is fixed, that is the principal branch > has to be called main (and couldn't be called say default?) Not an ELPA expert here but AFAIU the branch your community is using to produce releases can be called as you prefer, see the decription of :release-branch in README. > 2. Matlab is right now in MELPA and it seems much simpler to add a > package to MELPA than to ELPA. Is one of the reasons, the github > interface MELPA uses, but ELPA is bound to savannah that does not > provide something similar? I'm not sure why you think the MELPA process should be easier, adding emacs-matlab to ELPA should be like a three line patch to where we just specify package-name, url and release-branch no? You can submit the patch here or if these three parameters are known we can write and push the patch for you :) Thanks Andrea