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
I was deploying my emacs configuration on a new machine when I realized that recipe repositories are frozen in Radian.
This caused my config to fail since I just started using casual-dired which was just recently added to MELPA.
It's not such a big deal since I just did straight-pull-recipe-repositories, but I am wondering if it makes sense to not freeze the versions of recipe repositories or if there's a way to override their freezing (without directly modifying radian's versions.el)
The text was updated successfully, but these errors were encountered:
It's intended for recipe repositories to be part of the lockfile. Otherwise, the configuration isn't reproducible - packages may pull from different sources, packages may have been removed from the recipe repositories, etc.
What you want is a way to mark particular packages to be controlled by your radian-local lockfile, so that you can use your own versions versus what is upstream in Radian. That feature needs to be implemented in straight.el, which I haven't done yet.
I was deploying my emacs configuration on a new machine when I realized that recipe repositories are frozen in Radian.
This caused my config to fail since I just started using
casual-dired
which was just recently added to MELPA.It's not such a big deal since I just did
straight-pull-recipe-repositories
, but I am wondering if it makes sense to not freeze the versions of recipe repositories or if there's a way to override their freezing (without directly modifying radian'sversions.el
)The text was updated successfully, but these errors were encountered: