If a package is merged to rename should the main package use replaces?

ZenRen · 2021-07-29 17:59:26

I just took on an orphan, but it uses the wrong package naming scheme for its group. I assume the correct way to rename a package is to create a new package and merge the old one. Should the new package use the replaces= variable in the PKGBUILD, or will users be transferred to the new package automatically? I know the replaces variable should be avoided, so I wanted to make sure beforehand.

WorMzy · 2021-07-29 19:16:53

Replaces has no effect on AUR packages, except when the user builds the package and adds it to a package repository. Use conflicts and provides and add a note to the old package name before starting the merge process (in which you should similarly document the change). Those users who have subscribed to notifications will be alerted to your message about why the package has been renamed. Those that aren't can search the aur-requests mailing list (and find your merge request for information) when they notice that the original pkgname has vanished from the AUR.

ZenRen · 2021-07-29 21:16:10

Ok. I did mention in a comment that I am looking into renaming it. Best practice is to wait a week or so and then merge, add the old package name to conflicts and provides? In the meantime it won't matter that the renamed package is a duplicate?

Lone_Wolf · 2021-07-30 09:38:52

As long as it is clear why there are temporarily 2 packages it should not be a problem.

Arch Linux

#1 2021-07-29 17:59:26

If a package is merged to rename should the main package use replaces?

#2 2021-07-29 19:16:53

Re: If a package is merged to rename should the main package use replaces?

#3 2021-07-29 21:16:10

Re: If a package is merged to rename should the main package use replaces?

#4 2021-07-30 09:38:52

Re: If a package is merged to rename should the main package use replaces?

Board footer