From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Niklas Eklund Newsgroups: gmane.emacs.devel Subject: Re: Name dtache.el Date: Fri, 20 May 2022 15:19:13 +0000 (UTC) Message-ID: <7b7fb453-d2fa-4e72-a7f7-d6967813a291@posteo.net> References: <87y1zq5vt7.fsf@posteo.net> <87wnf56ix0.fsf@posteo.net> <87sfpt6ikz.fsf@posteo.net> <87zgjq33tb.fsf@posteo.net> <87a6bccmfh.fsf@posteo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="31511"; mail-complaints-to="usenet@ciao.gmane.io" Cc: rms@gnu.org, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri May 20 17:48:55 2022 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 1ns4s2-0007yx-LT for ged-emacs-devel@m.gmane-mx.org; Fri, 20 May 2022 17:48:54 +0200 Original-Received: from localhost ([::1]:57456 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ns4s1-0000rD-C1 for ged-emacs-devel@m.gmane-mx.org; Fri, 20 May 2022 11:48:53 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:59296) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ns4PQ-0001zB-By for emacs-devel@gnu.org; Fri, 20 May 2022 11:19:20 -0400 Original-Received: from mout01.posteo.de ([185.67.36.65]:60275) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ns4PO-0003bH-MT for emacs-devel@gnu.org; Fri, 20 May 2022 11:19:20 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 477B3240026 for ; Fri, 20 May 2022 17:19:16 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1653059956; bh=5T/S71tDchuQ0Zlg17FG6oFsE8IbU0tduARvIr9wHwE=; h=Date:From:To:Cc:Subject:From; b=iyoocTDHgOfQUm03KyCZM2VQKo2LzWYjCky5FvsR/AUwdUfNBsjCZREWbuOWJrmuY yYEDc9v3R8h2Fh1Hd8/0RhEkp6Ad9hrmvmANRQxxuLca/UDvTDltJLWL9jpw1AplPN AmhyW5lfDZJWeIV0pmOPwJK62b9iv5N7C1T4PMIWwJS8RFL7mYrwWrRT0/DXFKvaKm AXiVnsXi5tELztjYz686Df27Xu2E2gBKCT74kMy7Vg7gk3kkJBSrmXUVS3ORCf3PGi 5484QwTYz7w6NOORaahT2aLaf22pIHruviWSD4ZeD1g/dISnksNYEq2HaIAAZz7PO4 Z0VLBpcZUDZhQ== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4L4VkW0ypJz6tmS; Fri, 20 May 2022 17:19:14 +0200 (CEST) In-Reply-To: X-Correlation-ID: <7b7fb453-d2fa-4e72-a7f7-d6967813a291@posteo.net> Received-SPF: pass client-ip=185.67.36.65; envelope-from=niklas.eklund@posteo.net; 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Fri, 20 May 2022 11:46:23 -0400 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" Xref: news.gmane.io gmane.emacs.devel:290006 Archived-At: May 20, 2022 16:32:05 Stefan Monnier : > Niklas Eklund [2022-05-20 14:23:46] wrote: >> I have gotten around to update the name of the package from dtache -> >> detached.el. > > Is it really necessary? I think it's desirable to make the switch, even though I dislike the=20 annoyance it creates. I think its good to do the switch now then later=20 on. I have done commits renaming all the files and functions so updating the=20 package archives is the last step. >> I am not sure what to do about the name of the branch, if I was=20 >> suppose >> to update that or if a maintainer can do that to make it aligned with >> the new name. > > Renaming requires some manual tweaking, yes.=C2=A0 I can take care of tha= t. Great > But more importantly it's an annoyance for your users since updates > won't be applied for them, so they may end up stuck at the old > `dtache.el` release without realizing there's a new version under > a different name.=C2=A0 We currently don't have any way to inform > `package-update` and friends about a renaming :-( Yes, that's unfortunate of course. Since I merged the renames of files=20 and functions to the new names I thought that would indirectly inform=20 users about the change. Although those relying on releases won't get that information then. Maybe= =20 one solution to that is that I release a new version and only update the=20 recipe ones it has become available on ELPA? /Niklas