Bug#1138884: dh-elpa: simplify emacs-bundled addon handling
Sean Whitton <[email protected]>
| Newsgroups | gmane.linux.debian.devel.emacsen |
|---|---|
| Message-ID | <87mrx9z7lp.fsf__43434.3597431266$1780650581$gmane$org@melete.silentflame.com> |
control: severity -1 wishlist
Xiyue Deng [04/Jun 11:58pm -07] wrote:
> Currently dh-elpa has special handling of addons that are built-in to
> emacs so that instead of adding the addon to the Depends field, it adds
> emacs-common instead to fulfill the requirement. This has been causing
> issues that if an addon requires a version of the addon that is higher
> than the one bundled in emacs, dh-elpa will not know. As an example:
> recently a few packages start to require compat 31.0, while the current
> Emacs 30.2 bundles compat of version 30.2.9999. As dh-elpa does not
> handle the version, it still only provides emacs-common as part of
> "${elpa:Depends}". The current work around is to manually add
> "elpa-compat (>= 31.0)" to Depends of the addon package[1][2], which
> would be error-prone if there is no test to catch this.
>
> On the other hand, emacs-common generates breaks/replaces/provides for
> all bundled addons with their elpa-* names since 1:30.1+1-7. Using
> compat as an example, emacs-common will have the following:
>
> ,----
> | Break: elpa-compat (<< 30.2.9999)
> | Replaces: elpa-compat (<< 30.2.9999)
> | Provides: elpa-compat (= 30.2.9999)
> `----
>
> With this info, dh-elpa does not really have to do any special handling
> anymore, and just issuing the standard versioned elpa-compat as part of
> `${elpa:Depends}', and apt should do the right thing. Consider the
> following 2 cases:
>
> * emacs-git-modes depends on "elpa-compat (>= 29.1.4.1)"; emacs-common
> 30.2 provides a higher version of compat, so emacs-common can fulfill
> this dependency (you can also install elpa-compat 31.0.0.1 of course,
> which will also take precedence.)
>
> * transient depends on "elpa-compat (>= 31.0)"; emacs-common 30.2 cannot
> fulfill this requirement, so elpa-compat 31.0.0.1 will be installed.
>
> So it looks like after emacs 1:30.1+1-7, dh-elpa does not need to have
> special handling of bundled addons anymore.
>
> If this sounds good, I'll prepare an implementation.
Yes, I think you're right, we can change this now.
--
Sean Whitton
signature.asc
(application/pgp-signature, 869 B)
-----BEGIN PGP SIGNATURE----- iQJNBAEBCgA3FiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAmoij8IZHHNwd2hpdHRv bkBzcHdoaXR0b24ubmFtZQAKCRBpW3rkvwZiQFAFEAC8eamzfuvM7egDqpTA/gmS oddYf1z976dQyLHErw9QOC5+++cxuNG4kjpZWVqZCY4a5wObAlZ+3wWviX6kwxWQ c3jIgpJk03zNIvyqOSqWkxun3zhau4uq0t8XY2GPUQFrGr9hGx+HteOf7eBHvGDW Wa7PJXlsSGBNXMXUAJse5maKDIIS68mkItv8xdxS/JoGIesqh+UW8F0asgf3uzKL R7AB7hkkyYqURPH0X+5VwiVvUzhkcYTcYZhOe3BQacP0BQOQUbYBZJsKD86sjAol 6JRK750H0RLBSVyxQtcQ7ZC70tyhgoevhizrH92UOnjlvBjtB8Fm+Bl0MnaRb6ZU gIwSGZ+ThY0gpBrYBEiJXSFY8tgPwTkzK9EVaXg9a2FGvBmrxHdXNs/yWay8lsCs iaILd2IM1uWp1OK3aRVjRvcnB++6XUqWwFULgoj2p7ykJtXmgX8p1V4kwQe1WCLf 6hYCMSSIkS5DfpgUa5SSSrj8DrfXB5tzuwT7/oECeENaDmOH49PuzCxOtussl8/G XwOtmB8N6LLc7QKrIE8WxisO+Vkapos6Ivn8j5ZHwcYjCvaAwQAJ1KfJ/4CtgGdx A49fzMLWs23vB1AN7qjBc4P8wM+yQcIyY32IFMzttMF+z8Ukm/YEjhfcgCGgxoGO RRk2LzNiaHPp/BSEkVeaKA== =bqcE -----END PGP SIGNATURE-----