current ebuilds need a given mercurial version (in this case, 0.9.1) whereas mercurial itself is at 0.9.3 (unstable) already, so having all installed makes portage want to downgrade mercurial. besides bumping hgcommand/hgmenu, the more general question is whether there is a need at all for this specific dependency for these two packages (i.e., do mercurial commands/syntax change that break even between minor releases)? Reproducible: Always Steps to Reproduce:
The vim herd isn't interested in maintaining these -- I don't have any mercurial repos to test it with, for example. agriffis, who used to maintain these, has gone AWOL. Treecleaners, what do you say to giving these two the axe? Vim plugins are easy to install by hand in one's ~/.vim/ directory, and I'd like to keep the things that're in tree to the more widely used ones.
agriffis retired. They're not broken, so i don't see why they should be removed. Treecleaners, any thoughts?
i'd say it's up to the vim herd.
(In reply to comment #3) > i'd say it's up to the vim herd.(In reply to comment #1) > The vim herd isn't interested in maintaining these -- I don't have any > mercurial repos to test it with, for example. agriffis, who used to maintain > these, has gone AWOL. > > Treecleaners, what do you say to giving these two the axe? Vim plugins are easy > to install by hand in one's ~/.vim/ directory, and I'd like to keep the things > that're in tree to the more widely used ones. *shrug* If you really don't want 'em anymore, feel free to punt them (either way). You could also dump 'em onto maintainer-needed@g.o ..
> *shrug* If you really don't want 'em anymore, feel free to punt them (either > way). You could also dump 'em onto maintainer-needed@g.o .. Usually we don't remove packages from the tree if they are not broken. And if they are, we try to fix them first before punting them.
(In reply to comment #3) > i'd say it's up to the vim herd. > I say that I won't be maintaining them, I don't have any mercurial repos to test them with, and in general I'm trying to reduce the number of vim scripts that're in the tree, since they're so easy to install locally.
*mercurial-0.9.4 (04 Jul 2007) 04 Jul 2007; Andrew Ross <aross@gentoo.org> -mercurial-0.9.ebuild, -mercurial-0.9.1.ebuild, -mercurial-0.9.1-r1.ebuild, -mercurial-0.9.1-r2.ebuild, +mercurial-0.9.4.ebuild: Bump to 0.9.4 (bug #183212) and drop ebuilds <0.9.3 Now both these ebuilds have broken dependency tree on alpha/amd64/ia64/ppc/ppc64/sparc/x86 ? they depend on ~dev-util/mercurial-0.9.1
Both app-vim/hgcommand and app-vim/hgmenu should be punted, as they're part of the upstream mercurial tarball anyway and can easily be installed as part of dev-util/mercurial (either in /usr/share/doc/${P}/contrib/vim/ or using the vim-plugin eclass). mr_bones_ has already restored dev-util/mercurial-0.9.1-r2.ebuild to address the breakage I caused (sorry about that), and I'll keep it in the tree until hgcommand and hgmenu are removed.
Please vote; +1 here wrt the above comment.
i don't really care either way, i just complained about the generic portage dependency breakage that was caused by these packages ;-).
++
gone
