On 27/12/2020 02:30, alad via aur-general wrote:
On 26/12/2020 15:39, Michael Kogan via aur-general wrote:
Done, thanks! Eventually I did all of the above (a "replaces" field in the new package which seems to have no impact though, an echo output with the deprecation message, a deprecation message in the package description, a comment on the AUR page and an out of date notification with again a deprecation message). Let's see how it goes! :)
As mentioned, replace does nothing at all for AUR packages (unless you put them in a local repo).
You can add conflicts/replaces though, such that users don't have to manually remove the old package before installing the new one.
...and I meant conflicts/provides in the last part.