From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jonas Bernoulli Newsgroups: gmane.emacs.devel Subject: Re: elpa.git and `new-master` Date: Tue, 15 Dec 2020 22:43:00 +0100 Message-ID: <877dpi690b.fsf@bernoul.li> References: Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="7290"; mail-complaints-to="usenet@ciao.gmane.io" To: Stefan Monnier , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Dec 15 22:46:36 2020 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 1kpI9U-0001mE-GE for ged-emacs-devel@m.gmane-mx.org; Tue, 15 Dec 2020 22:46:36 +0100 Original-Received: from localhost ([::1]:47062 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kpI9T-0000Pc-Cn for ged-emacs-devel@m.gmane-mx.org; Tue, 15 Dec 2020 16:46:35 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36522) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kpI68-0007Hp-0W for emacs-devel@gnu.org; Tue, 15 Dec 2020 16:43:08 -0500 Original-Received: from mail.hostpark.net ([212.243.197.30]:57356) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kpI65-00009j-QT for emacs-devel@gnu.org; Tue, 15 Dec 2020 16:43:07 -0500 Original-Received: from localhost (localhost [127.0.0.1]) by mail.hostpark.net (Postfix) with ESMTP id 91FB9160CE; Tue, 15 Dec 2020 22:43:01 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bernoul.li; h= content-type:content-type:mime-version:message-id:date:date :references:in-reply-to:subject:subject:from:from:received :received; s=sel2011a; t=1608068581; bh=xNtEW3PSexGyenHTtMLLnJlC 8Az3jp2T+xVgNgqYBPI=; b=QCSmL8uWroaQl0ChnV3sxprSlpvFiFnbR3l9h9NC /k0S3FyUooRQEvr7488rGxHrTJYcIjF8TfX8sq6z4YaUCeJ+wjDv3+gryrPslAN+ ob0s5TBwdDqBudCLC4UuvxO7sgoE8u8WIDnih/5RNS78NLwq614lfDYuS5SwZg9G 4u8= X-Virus-Scanned: by Hostpark/NetZone Mailprotection at hostpark.net Original-Received: from mail.hostpark.net ([127.0.0.1]) by localhost (mail1.hostpark.net [127.0.0.1]) (amavisd-new, port 10224) with ESMTP id tvPIXBZ6nRPB; Tue, 15 Dec 2020 22:43:01 +0100 (CET) Original-Received: from customer (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.hostpark.net (Postfix) with ESMTPSA id 50E2B160E8; Tue, 15 Dec 2020 22:43:01 +0100 (CET) In-Reply-To: Received-SPF: none client-ip=212.243.197.30; envelope-from=jonas@bernoul.li; helo=mail.hostpark.net 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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:260933 Archived-At: Stefan Monnier writes: > As part of the effort to setup the NonGNU ELPA infrastructure, I've also > overhauled the GNU ELPA part. Thanks a lot for your work on this! > As a result, I decided to create a fresh `new-master` branch which > doesn't share its history with `master`. This new branch will replace > `master` in the coming days. Since you have to do this for this branch anyway, please also force-push to 'externals/transient' in order to discard the last few commits, which were only needed because the `:renames' property did not exist yet. Now that that is available, I plan to use transient's "master" branch and do the edits using `:renames' et al. > So whoever is tracking `master` will be faced with a > "non-fast-forward" update. This can be annoying and I apologize in > advance, but I think the long terms advantages largely make up for > the short term annoyance. I noticed that non-fast-forward pushes are disallowed (when trying to do the reset I just mentioned myself) and ended up wondering if there are any other checks in place that prevent other potential push errors. Most importantly what happens if someone has managed to merge the old "master" into the new one and then pushes that? That is a fast-forward, though one that we very much want to prevent. Is there some list with disallowed hashes? > - It also know how to generate Info files from Org manuals. > - It can even run `make` as part of building the tarballs, making it > possible to perform various massaging. > This obviously can't just run "anything you like" since it depends > on what's available on `elpa.gnu.org`, so if you want to use this > feature, please get in touch with me so we can coordinate it. I had some issues with this. Some of them are due to my packages needing some additional libraries to generate the *.texi files from the *.org input and I will contact you about that privately. But there was also one issue that might affect others: `org-texinfo-export-to-texinfo' may end up calling git (e.g. to get the version number), which requires access to the git (control) directory "ELPA/.git" (just "ELPA/.git/worktrees/" probably won't do), but currently bubblewrap is not given access to that. > - Another advantage is that the new code makes it much easier to build > your own tarballs, for example to test them before pushing to code. > You can just do `make build/[PKGNAME]` and the resulting package will > be built in `archive/[PKGNAME]-[VERSION].tar. That almost worked. "make build/" (or `elpaa--make-one-package') calls `elpaa--external-package-sync', which pulls. That of course is not desirable when one wants to test some other revision of the package than what would end up being pulled. Jonas