Package: dh-elpa
Version: 2.1.9
Severity: wishlist
A recent bug#1101304 shows some limitation of version handling of
dh-elpa for packages that are both built-in and packaged separately. Currently, dh-elpa can mark a package as packaged separately, and then
detect the version from an addon comment header, much like non-built-in packages. However, when a built-in package is sufficiently new, an
addon can directly depend on Emacs itself without requiring the
separately packaged version.
As an improvement to avoid requiring the separated packaged version, for
a package `foo' that is built-in, if the packaged version meets the requirement of an addon, ${elpa:Depends} can just generate "Emacs (>= <current version>)"; otherwise generate "elpa-foo (>= <required
version>)" as before.
Implementation wise, AFAIK there is no public API to query the version
of a built-in package, so for now one may need to inspect `package--built-versions' directly. Not sure whether upstream would implement an API for querying built-package versions.
Option 1 also sounds good to me.
This may also be useful to handle security update for stable version,
though I'm not sure whether it will automatically handle the upgrades.
(Wondering for the situation that Emacs version A provides foo 1.0, and
when foo 1.0 founds a security issue, and Emacs version A+deb12u1 fixes
it by providing foo 1.1, will foo 1.0 automatically upgrade to Emacs A+deb12u1, or it still requires user manually uninstalling foo 1.0?)
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 480 |
Nodes: | 16 (2 / 14) |
Uptime: | 05:04:11 |
Calls: | 9,535 |
Calls today: | 3 |
Files: | 13,653 |
Messages: | 6,138,642 |
Posted today: | 1 |