[aur-general] OK! changing a PKG's name and retaining votes/comments

[Dave Reisner]

On Fri, Jul 22, 2011 at 05:36:47PM +0300, cantabile wrote:
> On 07/22/2011 04:48 PM, member graysky wrote:
> >The whole point of my post was NOT about what to call packages or to
> >ignite a debate... it was about how to use the new functionality in
> >the AUR to move/rename/whatever existing packages to newly named ones.
> >  To quote the relevant section of my original post:
> >
> >1) What is the SOP for people to request a namechange?
> >2) What is critically important to include the PKGBUILD?
> >
> >My best-guess answers:
> >1) Upload the new PKGNAME as a new package and email a TU with the
> >old/new name or post to this mailing list.
> >2) Include a replaces statement in the PKGBUILD.  E.g.
> >replaces=('old_PKG_name').
> >
> >On Fri, Jul 22, 2011 at 8:52 AM, Ionut Biru<ibiru at archlinux.org>  wrote:
> >>On 07/22/2011 03:40 PM, Ike Devolder wrote:
> >>>
> >>>Op 22-07-11 13:35, member graysky schreef:
> >>>>
> >>>>I started a thread with same subject less the "OK! " back in May and
> >>>>am glad to see people saw some value in it to the point of modifying
> >>>>the AUR! Since the next version of the linux kernel is now released
> >>>>and likely soon to enter [testing] under a new name, I need to use
> >>>>this new feature to change the name of "kernel26-ck" in the AUR to
> >>>>"whatever-tpowa-uses-ck" -- at the risk of exposing my naiveté on the
> >>>>subject, I'll ask:
> >>>>
> >>>>1) What is the SOP for people to request a namechange?
> >>>>2) What is critically important to include the PKGBUILD?
> >>>>
> >>>>My best-guess answers:
> >>>>1) Upload the new PKGNAME as a new package and email a TU with the
> >>>>old/new name or post to this mailing list.
> >>>>2) Include a replaces statement in the PKGBUILD. E.g.
> >>>>replaces=('old_PKG_name').
> >>>>
> >>>>Thanks for the thoughts!
> ><SNIP>
> >>
> >>not again!
> >>
> >>stop this discussion now!. is settled, the next kernel package has _linux_
> >>pkgname
> >>
> >>--
> >>Ionuț
> >>
> As far as I know, there was some talk, there was a patch or two, but
> nothing was actually implemented.
> 

I think the consensus was that we were willing to migrate comments to
new packages, but that we wouldn't do flat out renames. Either way,
there was never anything committed.

d