Alec Warner wrote:
On the topic of old ebuilds; situations may arise where a particular
maintainer is trying to clean out a version of a package but finds
that $arch doesn't have anything newer stable and thus can't do any
sort of cleanup for fear of breaking $arch.
You will probably again state that maintainer should just leave the
older versions around. I will state that at least as a maintainer I'm
willing to do so for only a limited period of time. Otherwise it
becomes an annoyance when trying to clean up after packages to have
ebuilds from three or four minor versions ago lying around.
Now this is the exact situation that I'm wondering about. What's the
best thing to do?
The only thing I can come up with is, if there's an old ebuild that I
won't help support / maintain, but it's the latest stable for some arch,
then remove all the other arch keywords except that one. At least that
way, I won't have to worry about people from arches who *are* up to date
bugging me about it.
I'm not sure that's the best solution though. I can see the reasoning
behind "there's a newer stable version anyway, so they shouldn't use the
old one", but really ... it can get annoying having some "stable
request" bugs open for a very long time. If someone wants to donate me
more hardware, I'll get to working on those. :)
Steve
--
gentoo-dev@gentoo.org mailing list
