From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Thierry Volpiatto Newsgroups: gmane.emacs.devel Subject: Re: updating async on elpa Date: Sat, 01 May 2021 14:50:59 +0000 Message-ID: <87k0oi5wt3.fsf@posteo.net> References: <874kfom16w.fsf@posteo.net> <871rarn69c.fsf@posteo.net> <87y2czll5a.fsf@posteo.net> <87o8dvty56.fsf@posteo.net> <87zgxf5zyz.fsf@posteo.net> <87lf8zrqym.fsf@posteo.net> <87r1iqeh9m.fsf@rabkins.net> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3780"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Yoni Rabkin , emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat May 01 16:55:14 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 1lcr1W-0000ri-Ej for ged-emacs-devel@m.gmane-mx.org; Sat, 01 May 2021 16:55:14 +0200 Original-Received: from localhost ([::1]:34242 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lcr1V-0003SW-El for ged-emacs-devel@m.gmane-mx.org; Sat, 01 May 2021 10:55:13 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:50966) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lcr0z-00033p-3Y for emacs-devel@gnu.org; Sat, 01 May 2021 10:54:41 -0400 Original-Received: from mout02.posteo.de ([185.67.36.66]:36735) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lcr0x-0006PI-5Z for emacs-devel@gnu.org; Sat, 01 May 2021 10:54:40 -0400 Original-Received: from submission (posteo.de [89.146.220.130]) by mout02.posteo.de (Postfix) with ESMTPS id C8E932400FE for ; Sat, 1 May 2021 16:54:36 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1619880876; bh=dz46Z0SyB3ccUV4r4G6AB4KvD/BznGQ3VQ6gaiLDk4A=; h=From:To:Cc:Subject:Date:From; b=FGnHUc6my5T1W6xM/SYvzUq32iK6/EHK/93+UHYG4lZh6504kkiTrZkIPVoSm9uG6 SvW106Ri/MGnNjg8KzaRR3DdtCLdma0cnaoUrOqrzKWVKuQaBFA3ZRzySCNU/SmLxH MaNXLvbRKdl0Wl5LgECPURDFV9nJgZvR0HNzilsZjLJNy7AAp8RE6wUcXCxFLBdyIt D3SS8uduUnIRCFd5NNzddVDhK7eEmTlEZ2phE+PE2OfrnBhKtuTWEzMrUopwd12w0c xhRB3ojdKx7CaakaOaYIEGiQYR+eXBYsvKx7RO4qZlDfBlt6vMpaHnt2+7v0JwIpfX y8DlOAyfHOqYg== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4FXXMH2mcsz9rxB; Sat, 1 May 2021 16:54:35 +0200 (CEST) In-reply-to: Received-SPF: pass client-ip=185.67.36.66; envelope-from=thievol@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, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=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:268716 Archived-At: --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Stefan Monnier writes: > [[PGP Encrypted Part:OK]] >> Having one repository per package is how it works everywhere else >> (Savannah, etc.), and is easier to understand because of that. This is >> from the point of view of a contributor of course; I cannot speak to how >> it looks from Stefan's side. > > From my side it's plain and simply not an option at all because creating > a new repository on git.sv.gnu.org requires manual intervention from the > Savannah admins. Having had to design a solution that lives within this > constraint, I'm actually pretty happy about the current result, so if > the constraint were lifted, I'd probably want to try and preserve > the advantages. > > In any case the `:auto-sync` feature should make it much less of an issue. > >> I would be much happier if emms and rt-liberation had their own >> repositories since it would mean that I couldn't possibly break anything >> except emms or rt-liberation when I push to those projects in elpa. > > The `elpa.git` is configured to reject non-fast-forward pushes, which > should catch most blunders. Plus it is cloned at various different > places which are not all constantly updated, plus (almost) all changes > to it are reflected in the elpa-diffs mailing-list. So even if you do > manage to make some really terrible mistake it should be quite easy to > recover from it. Oh that's good and make me more confident, like Yoni I am always afraid of corrupting the elpa repo. > You might want to activate the `:auto-sync` on your packages, tho to > save you from the worry. Is this documented somewhere? =2D-=20 Thierry --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQHHBAEBCgAxFiEEI9twfRN7r3nig/xwDsVtFB0W75MFAmCNa6gTHHRoaWV2b2xA cG9zdGVvLm5ldAAKCRAOxW0UHRbvk+2wC/oCzCbYkV/b+k4bgqsXeAY85aSZkY+3 1S115TZ9W/qIW7qnC8y8Wxudp48NPmbksX3HSjGjvoUUT7MuEtVeFMTmt+xjD0lI gYpCsskC7rQltNPrhRn3B6MNQciUQUwTeCnNXzO+WKtG5elrrOcDxs+mmwfKmd26 JvQyFomdm9uMK+uwJY6itRuJVsO5X7JNGygywlRkuAR/mUx23mTXTdW7iw/ZQbsu 1qZHBar3AUiyGYxszsEstJkYawnp7amrcjxes5pOa5W4thNCf96oesiMtrCoTGf5 Afnd3rFZj5pC2WLVcKAquZZiqXnCKOmKLCPqs9vJxEj4aafrMNo7Fy7tGfcZ9tiC x4UIfKqyLfoOd7F8KM+EnrjjreuwzwxjH7eymoIgwaff1qrgstc8TSW5iersDHZz Avq/iY1dzUM6sOQbuNFIQRVFaOlSImGXiEp1L14owX8ax8N4HuKC4WUstSxKKXc3 577AuuDjpulXE91VRvJ+L22eS/57ojppfGQ= =/4uk -----END PGP SIGNATURE----- --=-=-=--