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: Request to add Package to GNU ELPA Date: Thu, 06 Apr 2023 13:41:35 +0200 Message-ID: <87bkk1jl00.fsf@bernoul.li> References: <87tty24ap2.fsf@bernoul.li> <87wn2y5em5.fsf@posteo.net> <87r0t44zbx.fsf@bernoul.li> <87sfde7lh4.fsf@posteo.net> <87lej6ju1m.fsf@bernoul.li> <875yaayyly.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="1075"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Philip Kaludercic Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Apr 06 14:01:06 2023 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 1pkOIc-000AdG-Fq for ged-emacs-devel@m.gmane-mx.org; Thu, 06 Apr 2023 14:01:06 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pkOHf-0005OA-9M; Thu, 06 Apr 2023 08:00:07 -0400 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 1pkNzr-0002Sr-3W for emacs-devel@gnu.org; Thu, 06 Apr 2023 07:41:43 -0400 Original-Received: from mail.hostpark.net ([212.243.197.30]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pkNzo-0004VQ-2b for emacs-devel@gnu.org; Thu, 06 Apr 2023 07:41:42 -0400 Original-Received: from localhost (localhost [127.0.0.1]) by mail.hostpark.net (Postfix) with ESMTP id 7F7EB164F8; Thu, 6 Apr 2023 13:41:36 +0200 (CEST) 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=1680781296; bh=2mp4ZPbarSSqUWSb8cG7eO1N K1ICrydJtlJdo0W93fI=; b=VSp7/08CKi8PG7wbrBGESJOBf8wmSkyn5EcgGoj2 E8uPU43D4/wM+6WpCgR0j/9YvLg/2UXHBaHTscqGauyb1aV0Bpd981izdzfbzV6n Xr7ORxV3yVWbHxrh+7J5UblHxQpiVbqW3pNcp7uf8nI9oZ2/HKCRV+3NDn1CP8tg X8M= X-Virus-Scanned: by Hostpark/NetZone Mailprotection at hostpark.net Original-Received: from mail.hostpark.net ([127.0.0.1]) by localhost (mail0.hostpark.net [127.0.0.1]) (amavisd-new, port 10224) with ESMTP id 0T3MtBluB8n7; Thu, 6 Apr 2023 13:41:36 +0200 (CEST) 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 37E8216524; Thu, 6 Apr 2023 13:41:36 +0200 (CEST) In-Reply-To: <875yaayyly.fsf@posteo.net> 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-Mailman-Approved-At: Thu, 06 Apr 2023 08:00:05 -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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:305142 Archived-At: Philip Kaludercic writes: >> I am hoping that someone would take charge of Package on Emacs' side, >> and bring some new momentum to its development. You would be a good >> candidate for that. ;D > > I am glad to help where I can (e.g. making sure that package.el can be > distributed on ELPA), but I don't know exactly what you have in mind > with the other changes so I would rather let you tackle those issues. Thanks. Once it is on ELPA, I can start propose backward compatible patches, and so can others. >>>> I had a look at vc-clone and a few vc-*-clone. They seem trivial >>>> enough to backport, either as part of Compat or in package-vc.el. >>> >>> [...] >> >> I assume that means "well it may *seem* that way, but if you are the one >> actually doing the work...". I know the feeling. oO > > I am not sure what you are talking about here? > > > [...] I was speculating on the meaning of the initial "[...]". Make of that what you want [...] ;P > But otherwise I would just try and avoid the need to force users to > upgrade. Upgrading should be incentivized with the advantages of doing > so, not the issues of (perhaps unconsciously) holding back. Sounds good. >> I would like to use a format that not only supported "pre-releases" but >> also "post-releases". Debian uses "post-releases" to implement >> "debian-revision" [1]; we could use it to separate the "timestamp" part >> from "latest released upstream version" part, in snapshot release >> version strings. [...] > > I cannot comment on this, but "post-releases" (as opposed to > "pre-releases") sounds like just another entry in `version-regexp-alist'? Unfortunately no. You cannot encode both pre- and post-releases using a flat list of integers only. (Unless you make one of them magical, but then you would better use a magical non-integer; which is exactly what I plan to do). I'll propose a patch to add nearly backward compatible support. > So to summarise, I think an approximate plan would be useful: > > 1. Update package.el to be published on ELPA > 2. (Optional) Update package-vc.el to be published on ELPA > 3. Specify and implement a new package-archives format > 4. Update package archives to generate the new archive format > > Anything I am forgetting? I don't think so. Well, it's "to ALSO generate the new archive format".