all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Bozhidar Batsov" <bozhidar@batsov.dev>
To: "Emacs Devel" <emacs-devel@gnu.org>
Subject: Re: Allowing rolling release packages on ELPA
Date: Mon, 24 Oct 2022 09:14:55 +0300	[thread overview]
Message-ID: <dfb1fe8f-65f3-40cb-902c-311b5234aea7@app.fastmail.com> (raw)
In-Reply-To: <874jvvm9hn.fsf@protesilaos.com>

[-- Attachment #1: Type: text/plain, Size: 2001 bytes --]

The patch seems fine to me, but I'm a bit skeptical about the whole rolling releases idea in general - e.g. should something like a change to the docs really result in a new release? How hard it is for people to actually update version timestamps themselves or to just stick to the *-devel repos if they don't want to cut releases?

How much was the demand for something like this in general? I can't think of any major Emacs package that does rolling releases.

On Sun, Oct 23, 2022, at 7:47 AM, Protesilaos Stavrou wrote:
> > From: Philip Kaludercic <philipk@posteo.net>
> > Date: Sat, 22 Oct 2022 10:31:35 +0000
> >
> > I have heard from people who prefer a rolling release model for their
> > packages, and requested that their packages not be added for {Non,}GNU
> > ELPA if they would have to update the version header manually,
> > presumably on every commit.  The following patch would enable ELPA
> > devel-like versioning on ELPA, if enabled with a :rolling-release
> > property.  WDYT?
> 
> Not a comment on the patch, but the idea behind it: I find the current
> arrangement between GNU ELPA and GNU-devel ELPA to give me the best of
> both worlds.  Users who need rolling releases can opt in to the "devel"
> version: this has the upside of explicitly acknowledging that the
> package is not marked as "stable".
> 
> The user can also arrange the 'package-archive-priorities' to choose
> gnu-devel by default.  And there is also 'package-pinned-packages' in
> case they want a different archive for a given package. Example from my
> init file where I prioritise regular GNU ELPA:
> 
>     (setq package-pinned-packages
>           '((cursory . "elpa-devel")
>             (denote . "elpa-devel")
>             (ef-themes . "elpa-devel")
>             (fontaine . "elpa-devel")
>             (lin . "elpa-devel")
>             (logos . "elpa-devel")
>             (pulsar . "elpa-devel")
>             (tmr . "elpa-devel")))
> 
> -- 
> Protesilaos Stavrou
> https://protesilaos.com
> 
> 

[-- Attachment #2: Type: text/html, Size: 3289 bytes --]

  parent reply	other threads:[~2022-10-24  6:14 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-22 10:31 Allowing rolling release packages on ELPA Philip Kaludercic
2022-10-23  4:47 ` Protesilaos Stavrou
2022-10-23  8:43   ` Philip Kaludercic
2022-10-24  6:14   ` Bozhidar Batsov [this message]
2022-10-24  6:45     ` Jostein Kjønigsen
2022-10-24  8:07       ` Bozhidar Batsov
2022-10-24 14:06       ` Stefan Kangas
2022-10-26 19:18         ` Richard Stallman
2022-10-24 16:00       ` Philip Kaludercic
2022-10-24 16:39         ` Jostein Kjønigsen
2022-10-26 19:18           ` Richard Stallman
2022-10-24 19:27         ` Stefan Monnier
2022-10-24 15:58     ` Philip Kaludercic
2022-10-24 17:27     ` Stephen Leake
2022-10-24 19:40 ` Stefan Monnier
2022-10-26  6:32   ` Philip Kaludercic
2022-10-26 11:57     ` Stefan Monnier
2022-10-26 15:27       ` Philip Kaludercic
2022-10-26 18:31       ` Philip Kaludercic
2022-10-26 18:55         ` Stefan Monnier
2022-10-26 19:07           ` Philip Kaludercic
2022-10-25 20:14 ` Richard Stallman
2022-10-26  5:10   ` Bozhidar Batsov
2022-10-26  6:30     ` Philip Kaludercic
2022-10-26  8:05       ` Bozhidar Batsov
2022-10-26 19:18       ` Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2022-10-26  5:58 Payas Relekar
2022-10-26  8:07 ` Bozhidar Batsov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=dfb1fe8f-65f3-40cb-902c-311b5234aea7@app.fastmail.com \
    --to=bozhidar@batsov.dev \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.