From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Philip Kaludercic Newsgroups: gmane.emacs.devel Subject: Re: Updating the "ELPA Protocol" Date: Wed, 16 Nov 2022 07:35:44 +0000 Message-ID: <87mt8r8i7j.fsf@posteo.net> References: <164484721900.31751.1453162457552427931@vcs2.savannah.gnu.org> <83y1soypvx.fsf@gnu.org> <87y1song5x.fsf@posteo.net> <83v8nsyof7.fsf@gnu.org> <87leoond7l.fsf@posteo.net> <83r0yfzz01.fsf@gnu.org> <87bkpjyx3p.fsf@posteo.net> <83bkpjynmj.fsf@gnu.org> <87iljqya44.fsf@posteo.net> <8335auzo9s.fsf@gnu.org> <87zgd2ws8z.fsf@posteo.net> <831qqezkxj.fsf@gnu.org> <87y1slgq3m.fsf@posteo.net> <87bkpgfsqv.fsf@posteo.net> <87educ9fei.fsf@posteo.net> <87y1sk7xtg.fsf_-_@posteo.net> <87h6z0rnuz.fsf@posteo.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="16441"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Stefan Monnier , Eli Zaretskii , rms@gnu.org, emacs-devel@gnu.org, Lars Ingebrigtsen To: Stefan Kangas Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Nov 16 08:36:47 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 1ovCyU-00044y-PJ for ged-emacs-devel@m.gmane-mx.org; Wed, 16 Nov 2022 08:36:46 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ovCxg-0001sI-AF; Wed, 16 Nov 2022 02:35:56 -0500 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 1ovCxb-0001rp-68 for emacs-devel@gnu.org; Wed, 16 Nov 2022 02:35:52 -0500 Original-Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ovCxY-00085J-SO for emacs-devel@gnu.org; Wed, 16 Nov 2022 02:35:50 -0500 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 4AEB924002B for ; Wed, 16 Nov 2022 08:35:46 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1668584146; bh=Uzy+cwL0oHZ7Ok3SXB20vlvaL61fojFl8X5w3RdNZcI=; h=From:To:Cc:Subject:Date:From; b=Ku1CjbjpzOrxaVMUsRkTNlmpDVj+d8lEab1tpTHarQsmNEArbQlUIlSBK9VR1QpWz JV809xPRlYTD0HKlO0d6tnfliXKhos8YEN1YuJm947Sf76QyE075Zq6Ah4Vm/rBL7w 3zVgQ0SR/vujYdfdM7/TpzxXHODN/hs+hC/u7yCT011kaGVc6qLMtD3/yX1p95SFwB VklTI8FM+C6jA6IS9Us7wNn//ErZgAdqrvaHL5bSzY6mD4t4QBRgH/WH010ZtZr6UK NS/jKP60+if6mOBF1bjmytAlUymnRNcJkML0qBGwNal6K7WYmxqUyY90e2cqiueG4a /d2sLtW1XA4dA== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4NBvwd0yktz9rxY; Wed, 16 Nov 2022 08:35:45 +0100 (CET) In-Reply-To: (Stefan Kangas's message of "Tue, 15 Nov 2022 12:41:51 -0800") Received-SPF: pass client-ip=185.67.36.65; envelope-from=philipk@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 autolearn=ham autolearn_force=no X-Spam_action: no action 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:299902 Archived-At: Stefan Kangas writes: > Philip Kaludercic writes: > >> One issue I have been told is the issue of renaming a package, so that >> package.el can transparently handle the rename. That appears to not be >> supported. > > How about using something like Debian's transitional packages, where you > replace the old package with an empty package that just depends on the > new package? Would that work? It might, but then the user is required to remove the old package and select the new one, right?