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:36:22 +0000 (UTC) Message-ID: References: <87y1zq5vt7.fsf@posteo.net> <87wnf56ix0.fsf@posteo.net> <87sfpt6ikz.fsf@posteo.net> <87zgjq33tb.fsf@posteo.net> <87a6bccmfh.fsf@posteo.net> <7b7fb453-d2fa-4e72-a7f7-d6967813a291@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="25302"; 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:47:46 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 1ns4qw-0006NY-0j for ged-emacs-devel@m.gmane-mx.org; Fri, 20 May 2022 17:47:46 +0200 Original-Received: from localhost ([::1]:56274 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ns4qu-000858-UG for ged-emacs-devel@m.gmane-mx.org; Fri, 20 May 2022 11:47:44 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35648) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ns4g1-0002DT-06 for emacs-devel@gnu.org; Fri, 20 May 2022 11:36:29 -0400 Original-Received: from mout02.posteo.de ([185.67.36.66]:60641) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ns4fz-0006rP-1T for emacs-devel@gnu.org; Fri, 20 May 2022 11:36:28 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id D95C824010A for ; Fri, 20 May 2022 17:36:24 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1653060984; bh=CEFwLv9PQdaLglH7jiOZc2+2WTmulshQMmK9eaR7GC4=; h=Date:From:To:Cc:Subject:From; b=IvA81WZ5gd+I2aaiEOBEbmkmBs0cwRmBvh6ArehEWIna6Nn1aF07dqfauebGUfcRp kB1CNoyRmfZ9OeEHepKhUMRRMvyk34Rc2eJHfJYYVYvfDSiNJdbWkiJA86xbkXEbdZ UK4ifRqTlMdc2qiZYjAMqY8QaTceaqC9OiH1q1WZy2cAHMog9XkoDfhe3MhNmD82kC hXhlYOhy6ZaTDMSNqkMRHbk06TauERjXVpPIL+M1D3awfcLX1XZv6VaYOUDyFxs9Zw jxoLXJtHjEVyNeA1JxIS/OMoX+2JqMZowOMSw6i1wupoQf4UYEJYbC13qRi4SwlYyp 0f+IRmMVuRU+w== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4L4W6H68nNz6tmb; Fri, 20 May 2022 17:36:23 +0200 (CEST) In-Reply-To: X-Correlation-ID: Received-SPF: pass client-ip=185.67.36.66; envelope-from=niklas.eklund@posteo.net; helo=mout02.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:290005 Archived-At: May 20, 2022 17:25:24 Stefan Monnier : >> Although those relying on releases won't get that information then.=20 >> Maybe >> one solution to that is that I release a new version and only update=20 >> the >> recipe ones it has become available on ELPA? > > A partial solution is to make a release of `detached.el` and once=20 > that's > done, make a release of `dtache.el` which `Package-Requires: ((detached= =20 > "??"))` Would I then need to have two different git repositories or how would you= =20 go about doing that? > It can made of a mostly empty file or a file containing just=20 > compatibility aliases. So would we then keep both dtache and detached in the elpa-packages file=20 or how would that work? Another option I could think about is making a release of the package at=20 its current path https://git.sr.ht/~niklaseklund/dtache which will be its= =20 last dtache release. But just before the release I add a commit that=20 issues a warning that if you are running this release you are tracking=20 the wrong patch. Then after the release, I remove that warning. Rename the https path to=20 detached.el and make a release with the new package name. Then it should be fine to update elpas tracking. Because if they run on=20 the old release the should have the warning that they need to upgrade.=20 What do you think? /Niklas but embedding a warning when it loads that > > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Stefan