I'm glad the patch looks fine, though I'm not sure I understand the issue about dependencies?
Well, AUR packages can depend on other AUR packages. If an AUR package is renamed which is itself a dependency, packages that depend on the old package name will be broken. On Wed, Jun 1, 2011 at 3:00 PM, Daenyth Blank <daenyth+arch@gmail.com> wrote:
This patch leaves the pkgname in the PKGBUILD as the old name. Probably not an issue, but the maintainer would have to submit an updated PKGBUILD after the name change.
That also seems to be valid for the dependencies=() array in depending PKGBUILDs. I suggest allowing renaming a package and marking it as out of date at the same time to have the PKGBUILD updated. Also all packages that depend on the renamed package should be marked out of date with an automatic comment that the dependency was renamed. regards mar77i