From: Jonas Bernoulli <jonas@bernoul.li>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: Request to add Package to GNU ELPA
Date: Thu, 06 Apr 2023 13:41:35 +0200 [thread overview]
Message-ID: <87bkk1jl00.fsf@bernoul.li> (raw)
In-Reply-To: <875yaayyly.fsf@posteo.net>
Philip Kaludercic <philipk@posteo.net> 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".
next prev parent reply other threads:[~2023-04-06 11:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 13:42 Request to add Package to GNU ELPA Jonas Bernoulli
2023-03-30 16:40 ` Felician Nemeth
2023-03-30 17:37 ` Philip Kaludercic
2023-03-30 17:32 ` Philip Kaludercic
2023-03-31 17:15 ` Jonas Bernoulli
2023-04-05 8:59 ` Philip Kaludercic
2023-04-05 14:13 ` Jonas Bernoulli
2023-04-05 18:07 ` Philip Kaludercic
2023-04-05 18:26 ` Philip Kaludercic
2023-04-05 21:08 ` Philip Kaludercic
2023-04-06 15:46 ` Philip Kaludercic
2023-04-06 21:36 ` Stefan Monnier
2023-04-07 7:23 ` Philip Kaludercic
2023-04-07 15:39 ` Stefan Monnier
2023-04-08 8:24 ` Philip Kaludercic
2023-04-09 15:29 ` Stefan Monnier
2023-04-09 17:27 ` Philip Kaludercic
2023-04-07 10:07 ` Philip Kaludercic
2023-04-06 11:41 ` Jonas Bernoulli [this message]
2023-04-17 16:24 ` Adding package-vc to ELPA Philip Kaludercic
2023-09-16 17:20 ` Stefan Kangas
2023-09-17 8:02 ` Philip Kaludercic
2023-03-30 19:10 ` Request to add Package to GNU ELPA chad
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bkk1jl00.fsf@bernoul.li \
--to=jonas@bernoul.li \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).