From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: Allowing rolling release packages on ELPA
Date: Mon, 24 Oct 2022 15:40:05 -0400 [thread overview]
Message-ID: <jwvk04p6muc.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87o7u4p2t4.fsf@posteo.net> (Philip Kaludercic's message of "Sat, 22 Oct 2022 10:31:35 +0000")
Hi Philip,
> presumably on every commit. The following patch would enable ELPA
> devel-like versioning on ELPA, if enabled with a :rolling-release
> property. WDYT?
[ I can imagine cases where we may need to explicitly set the "base version"
from which the rolling-release version is computed, but we can cross
this bridge when/if we get there. ]
I would suggest to add a mention in the doc saying that this
is discouraged.
Also, it should say that it is not compatible with `:release-branch`
and we should signal an error if `:release-branch` is set. Or maybe
make it a special value of `:release-branch` rather than a new keyword?
More importantly, it would be good to notice when that flag is out of
date, i.e. signal an error if the `Version:` has changed when that flag
is set. Maybe simply require that flag to be set to a string (rather
than just `t`) which is the expected version specified in `Version:` and
then signal an error if they don't agree?
Stefan
next prev parent reply other threads:[~2022-10-24 19:40 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
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 [this message]
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=jwvk04p6muc.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.net \
/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.