yeah, this is an old app, but still very popular I forked it on github, applied the gentoo patches and reworked the build system, but there is not going to be a major new release any time soon. I would not want to stabilize that new version just now. However, due to the nature of this package we should drop the stable keywords and remove the old ebuild. This might be against some policy, but who cares. The user expects "arch" to be stable, but it's not (anymore) in this case.
Why don't you simply package.mask the stable version, as is practice already, so that users actually see the reason it is going to be removed, and then remove it after 30 days. Your mask message would also inform users of the new unstable 0.2.1, of course, and refer to this bug report. Removing stable keywords first is not needed.
+ 21 Dec 2012; Julian Ospald <hasufell@gentoo.org> + -pornview-0.2.0_pre1-r2.ebuild, -files/pornview-0.2.0_pre1-4.diff, + -files/pornview-0.2.0_pre1-autoconf.patch, + -files/pornview-0.2.0_pre1-desktop-entry.patch, + -files/pornview-0.2.0_pre1-fix-array-boundaries.patch, + -files/pornview-0.2.0_pre1-fix-segfault-comment.patch, + -files/pornview-0.2.0_pre1-libpng15.patch, + -files/pornview-0.2.0_pre1-new-gtk-object-system.diff, + -files/pornview-0.2.0_pre1-underlinking.patch, -files/traypatch.diff: + remove old
