From: Phil Sainty <psainty@orcon.net.nz>
To: Tim Cross <theophilusx@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: PACKAGE-FEATURES, and hot update of Emacs packages
Date: Sun, 28 Nov 2021 17:23:21 +1300 [thread overview]
Message-ID: <d65e83c163e6861d50af869299b7f59d@webmail.orcon.net.nz> (raw)
In-Reply-To: <87a6hpkrj5.fsf@gmail.com>
On 2021-11-28 14:04, Tim Cross wrote:
> While I like the idea of being able to use package version to help
> manage this, the problem is there is no standardisation of package
> version formats. This makes calculation of which version is
> before/after
> another version unreliable.
Version comparisons are very well defined; but I guess you're referring
to MELPA's horribly-broken approach to versions here? A test with a
package installed from MELPA confirms that `package-desc-version' and
`package-get-version' do pick up on whatever version MELPA assigned, so
I guess that's unreliable as you say. Along with my earlier misgivings
about assuming that any given library had been installed as a package in
the first place, I agree that this doesn't seem like a viable approach.
The code itself would include the *real* version number, though, so in
principle I think it would be possible to utilise that; but I think it's
currently only exposed in the .el source.
If the .elc file contained the version number as well, I think that
load-time version-update tracking would become possible?
-Phil
next prev parent reply other threads:[~2021-11-28 4:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-27 9:31 PACKAGE-FEATURES, and hot update of Emacs packages Qiantan Hong
2021-11-27 10:09 ` Eli Zaretskii
2021-11-27 10:18 ` Qiantan Hong
2021-11-27 10:20 ` Qiantan Hong
2021-11-27 12:16 ` Phil Sainty
2021-11-27 13:30 ` Phil Sainty
2021-11-27 20:36 ` Qiantan Hong
2021-11-28 7:22 ` Phil Sainty
2021-11-28 7:51 ` Qiantan Hong
2021-11-28 1:04 ` Tim Cross
2021-11-28 4:23 ` Phil Sainty [this message]
2021-11-28 5:12 ` Stefan Monnier
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=d65e83c163e6861d50af869299b7f59d@webmail.orcon.net.nz \
--to=psainty@orcon.net.nz \
--cc=emacs-devel@gnu.org \
--cc=theophilusx@gmail.com \
/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).