From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: "Bozhidar Batsov" Newsgroups: gmane.emacs.devel Subject: Re: Update of ELPA package guess-language Date: Thu, 26 Aug 2021 08:31:08 +0300 Message-ID: <8a1057dd-3eea-4d95-b6c4-7f036b22bca3@www.fastmail.com> References: <87y28s8mi0.fsf@posteo.de> <87sfyx9602.fsf@posteo.net> <87y28phgyx.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=1aafbec9b4e644afbfc1c32c7445df8f Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="18265"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Cyrus-JMAP/3.5.0-alpha0-1125-g685cec594c-fm-20210825.001-g685cec59 To: "Emacs Devel" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Aug 26 07:32:48 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 1mJ80M-0004SP-Py for ged-emacs-devel@m.gmane-mx.org; Thu, 26 Aug 2021 07:32:48 +0200 Original-Received: from localhost ([::1]:49846 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mJ80L-0001MP-1M for ged-emacs-devel@m.gmane-mx.org; Thu, 26 Aug 2021 01:32:45 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42538) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mJ7zF-0000g1-4f for emacs-devel@gnu.org; Thu, 26 Aug 2021 01:31:37 -0400 Original-Received: from out3-smtp.messagingengine.com ([66.111.4.27]:56849) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mJ7zA-00087X-B9 for emacs-devel@gnu.org; Thu, 26 Aug 2021 01:31:36 -0400 Original-Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 988A25C009F for ; Thu, 26 Aug 2021 01:31:30 -0400 (EDT) Original-Received: from imap43 ([10.202.2.93]) by compute4.internal (MEProxy); Thu, 26 Aug 2021 01:31:30 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=batsov.dev; h= mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm1; bh=KHs2aP73Ormn/Ezahc1sIaz8XGLpf6c Ei/pFT9dZKVM=; b=SxrXKprm8Yzg6BLCtiQN17XS0pjZ+QWDLF8nPUnGQIniRa+ Nhh5kFiAE4kxnJhpeZDl9ehBbYtmWi8AXWsLyWcORK0ZPu8+mDYWAbBcnSKwPkXu r7f/MOf1Q0nHxUUPAkQh1a7ingHP/683R6wZTizdYvUlJZFGlehRYdvpML4NsHAm EeWri/ywim+Wv4Sek7Nkv/8ikea8l1dZhibi94HqWXZJgZVURivR7b5iSqUpeXgy EpkJIdbzfVHkGggReNNoURnLoPzzBfd2+Ry3GfB8JqdAz8P3efrOXDBvVtDTWZlO 66R3xKaYpQuZ9UxhX2WcyQbYFZDdnKqUdAsV8ZA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=KHs2aP 73Ormn/Ezahc1sIaz8XGLpf6cEi/pFT9dZKVM=; b=sySyIq3U/LqzsU4uvPp7Ok s8TAFuolpH8e/juBEGZ0ZNt6dWwiPrDoCvb5BeF5ZD+t7PxVxaVL06kGvzniyACr 7hmKX5+4HfWUUN1zJMJIDDD1fwMhAmPilauEHLoi58djnLXlitLDu1e2o2FhySEU 2+hP9L5ey/orAHbyM/qQTmz4DxVJAcyHCNsWnfgfb8CmTnlx9qPqTYlpQelw+pGI gnbzYfVTeFiH2zHV2cwXsoDz+MFiFsOLGWZy645DbqYxcvlUReOs+tzwtz5PZDJr uluF71eX2Kt8sEqS19zYaG9BPBYzsuHGfIzJ4v5/fgDfvqc3uDtqh5TfEW+HMRuw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddruddutddgleejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesrgdtreerreerjeenucfhrhhomhepfdeuohii hhhiuggrrhcuuegrthhsohhvfdcuoegsohiihhhiuggrrhessggrthhsohhvrdguvghvqe enucggtffrrghtthgvrhhnpeelheetieethfdtleehheejvddttddvveevvdetjeehjeet veehleduffehteegudenucffohhmrghinhepghhnuhdrohhrghenucevlhhushhtvghruf hiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegsohiihhhiuggrrhessggrthhs ohhvrdguvghv X-ME-Proxy: Original-Received: by mailuser.nyi.internal (Postfix, from userid 501) id 1FF86AC0362; Thu, 26 Aug 2021 01:31:30 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface In-Reply-To: <87y28phgyx.fsf@gnu.org> Received-SPF: pass client-ip=66.111.4.27; envelope-from=bozhidar@batsov.dev; helo=out3-smtp.messagingengine.com X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-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:272998 Archived-At: --1aafbec9b4e644afbfc1c32c7445df8f Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: quoted-printable > 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? 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 re= pository > >> but it=E2=80=99s not entirely clear to me how I can update the ELPA= version. > >> 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 tha= t really > >> true? I=E2=80=99m asking because I rarely see such requests here a= nd because > >> it=E2=80=99s not a terribly efficient workflow. Is there no way th= at ELPA > >> can automatically pull changes from the original repository? > > > > It should be possible, some package specifications (see elpa-package= s) > > 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.ht= ml >=20 >=20 --1aafbec9b4e644afbfc1c32c7445df8f Content-Type: text/html;charset=utf-8 Content-Transfer-Encoding: quoted-printable
But maybe adding :auto-sync t is needed = for GNU ELPA.

Seems like a pru= dent 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 cha= nges that are not properly copyrighted might make their way into GNU ELP= A?

On Wed, Aug 25, 2021, at 2:51 PM, Tassilo Ho= rn wrote:
P= hilip Kaludercic <philipk@poste= o.net> writes:

>> A while ago = I contributed the package guess-language to ELPA [1].  In
=
>> the meantime, I=E2=80=99ve added some improvements in my o= wn git repository
>> but it=E2=80=99s not entirely c= lear to me how I can update the ELPA version.
>> Fro= m reading the ELPA README [2], it seems that I have to request an
>> update on this list every time there is (significant-en= ough) change
>> in my repo (since I wasn=E2=80=99t g= iven push permissions).  Is that really
>> true= ?  I=E2=80=99m asking because I rarely see such requests here and b= ecause
>> it=E2=80=99s not a terribly efficient work= flow.  Is there no way that ELPA
>> can automat= ically pull changes from the original repository?
>
=
> It should be possible, some package specifications (see = elpa-packages)
> are given the :auto-sync attribute, bu= t I am not sure what the
> conditions are for a package= to be granted this status.

I can't find do= cs for :auto-sync.  Is that still in use, i.e., is there
<= div>any behavior associated with it?  At least Stefan said in [1] t= hat
auto-sync is effective for all packages in NonGNU ELPA= .  And indeed, I
can testify that changing stuff in m= y upstream repo and increasing the
Version will trigger a = new NonGNU ELPA release.

But maybe adding := auto-sync t is needed for GNU ELPA.

Bye,
Tassilo


--1aafbec9b4e644afbfc1c32c7445df8f--