|
From: | Niklas Eklund |
Subject: | Re: Name dtache.el |
Date: | Fri, 20 May 2022 15:19:13 +0000 (UTC) |
May 20, 2022 16:32:05 Stefan Monnier <monnier@iro.umontreal.ca>:
Niklas Eklund [2022-05-20 14:23:46] wrote:I have gotten around to update the name of the package from dtache -> detached.el.Is it really necessary?
I think it's desirable to make the switch, even though I dislike the annoyance it creates. I think its good to do the switch now then later on.
I have done commits renaming all the files and functions so updating the package archives is the last step.
I am not sure what to do about the name of the branch, if I was supposeto update that or if a maintainer can do that to make it aligned with the new name.Renaming requires some manual tweaking, yes. I can take care of that.
Great
But more importantly it's an annoyance for your users since updates won't be applied for them, so they may end up stuck at the old `dtache.el` release without realizing there's a new version under a different name. We currently don't have any way to inform `package-update` and friends about a renaming :-(
Yes, that's unfortunate of course. Since I merged the renames of files and functions to the new names I thought that would indirectly inform users about the change.
Although those relying on releases won't get that information then. Maybe one solution to that is that I release a new version and only update the recipe ones it has become available on ELPA?
/Niklas
[Prev in Thread] | Current Thread | [Next in Thread] |