You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Example problem: When a built-in dependency has newer version available on ELPA, and the newer version is specified in the Package-Requires of our package, the newer version is not installed, and makem tests our package using the older, built-in version.
makem could call package-install to install the library as a package, which would use the built-in machinery to install dependencies at their correct versions.
The text was updated successfully, but these errors were encountered:
Thanks. I think this is technically a bug, because even if --install-deps is used, that won't cause a built-in package to be upgraded to the ELPA version. It just happens rarely in practice (so far, anyway--it's likely to happen more often as more core packages are also put on ELPA).
IIUC, this bug is causing the hyperdrive.elbuild manifests to fail since the tests are running with the built-in version instead of the latest version which includes this fix.
Closed #41 as completed via d13527f.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.
Example problem: When a built-in dependency has newer version available on ELPA, and the newer version is specified in the
Package-Requires
of our package, the newer version is not installed, and makem tests our package using the older, built-in version.makem
could callpackage-install
to install the library as a package, which would use the built-in machinery to install dependencies at their correct versions.The text was updated successfully, but these errors were encountered: