From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Titus von der Malsburg Newsgroups: gmane.emacs.devel Subject: Re: Update of ELPA package guess-language Date: Thu, 26 Aug 2021 09:07:46 +0000 Message-ID: <87ilzs4lp0.fsf@posteo.de> References: <87y28s8mi0.fsf@posteo.de> <87sfyx9602.fsf@posteo.net> <87y28phgyx.fsf@gnu.org> <8a1057dd-3eea-4d95-b6c4-7f036b22bca3@www.fastmail.com> 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="14177"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Bozhidar Batsov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Aug 26 11:09:43 2021 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 1mJBOJ-0003Rv-04 for ged-emacs-devel@m.gmane-mx.org; Thu, 26 Aug 2021 11:09:43 +0200 Original-Received: from localhost ([::1]:47304 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mJBOG-00016e-Tn for ged-emacs-devel@m.gmane-mx.org; Thu, 26 Aug 2021 05:09:40 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:52106) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mJBNi-0000S7-Qb for emacs-devel@gnu.org; Thu, 26 Aug 2021 05:09:07 -0400 Original-Received: from mout01.posteo.de ([185.67.36.65]:52873) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mJBNg-00012a-Kg for emacs-devel@gnu.org; Thu, 26 Aug 2021 05:09:06 -0400 Original-Received: from submission (posteo.de [89.146.220.130]) by mout01.posteo.de (Postfix) with ESMTPS id CB2B4240028 for ; Thu, 26 Aug 2021 11:09:01 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1629968941; bh=FEEiZ5I4GxsV0YdNrjh8vPhCVcPyd5sGZoYKFXjvT/s=; h=From:To:Cc:Subject:Date:From; b=NtfYa4Ggrvxp/LMgWVqU+n1WhTBDia0/icudJVyJb5VU+NK156dELB3nC1L++WLuf KnnzyqsbfuFgcWodtQrddRl1hvDj775Ya/ODBhGLOJ0cA5dLB9tW7nYLLpvZPgPhMD oqpivfVPzlVzF8Lae279xv2wtdYMiw8ykfaecZaAbVsj01b5vKthpe8UATbV74lHvq Y+2eQMyhmyr40b2VkQ3q3KfoZpLITnZ+08XB3EtLzDi78b8hSh5VZhQsQWYsqLhHtv 4ttvqPzRokPy7CgK4Zj3caKc4XVtf39Bdj0f5aovU/hpM3E86CBlNJioWwNPI79Pk0 W6j05HS87rVSw== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4GwH8X6Bw7z6tmJ; Thu, 26 Aug 2021 11:09:00 +0200 (CEST) In-reply-to: <8a1057dd-3eea-4d95-b6c4-7f036b22bca3@www.fastmail.com> Received-SPF: pass client-ip=185.67.36.65; envelope-from=malsburg@posteo.de; helo=mout01.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, 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:273019 Archived-At: On 2021-08-26 Thu 08:31, "Bozhidar Batsov" wrote: >> But maybe adding :auto-sync t is needed for GNU ELPA. > > Seems like a prudent idea to me. I was surprised to learn that GNU > ELPA and NonGNU ELPA behave differently in this regard. Perhaps > there's some concern that changes that are not properly copyrighted > might make their way into GNU ELPA? Yes, and in my specific case the copyright situation is indeed unclear, whi= ch means that it would have been a mistake to automatically fetch the chang= es. Titus > > On Wed, Aug 25, 2021, at 2:51 PM, Tassilo Horn wrote: >> Philip Kaludercic writes: >>=20 >> >> A while ago I contributed the package guess-language to ELPA [1]. In >> >> the meantime, I=E2=80=99ve added some improvements in my own git repo= sitory >> >> but it=E2=80=99s not entirely clear to me how I can update the ELPA v= ersion. >> >> From reading the ELPA README [2], it seems that I have to request an >> >> update on this list every time there is (significant-enough) change >> >> in my repo (since I wasn=E2=80=99t given push permissions). Is that = really >> >> true? I=E2=80=99m asking because I rarely see such requests here and= because >> >> it=E2=80=99s not a terribly efficient workflow. Is there no way that= ELPA >> >> can automatically pull changes from the original repository? >> > >> > It should be possible, some package specifications (see elpa-packages) >> > are given the :auto-sync attribute, but I am not sure what the >> > conditions are for a package to be granted this status. >>=20 >> I can't find docs for :auto-sync. Is that still in use, i.e., is there >> any behavior associated with it? At least Stefan said in [1] that >> auto-sync is effective for all packages in NonGNU ELPA. And indeed, I >> can testify that changing stuff in my upstream repo and increasing the >> Version will trigger a new NonGNU ELPA release. >>=20 >> But maybe adding :auto-sync t is needed for GNU ELPA. >>=20 >> Bye, >> Tassilo >>=20 >> [1] https://lists.gnu.org/archive/html/emacs-devel/2021-08/msg00533.html >>=20 >>=20