vcscommand beta19 was released on 2007/07/31.
Did you try changing the name of the ebuild, running "ebuild path/to/ebuild digest" in a local overlay and then emerging? Use /usr/local/portage for a local overlay, and please see man 5 emerge and man portage.
Thanks, I'm familiar with ebuild, emerge, etc. Anything after beta16 is not yet mirrored, though, which is why a trivial move & re-digest is bound to fail.
(In reply to comment #2) > Anything after beta16 is not yet mirrored, though, which is why a trivial > move & re-digest is bound to fail. > OK, I guess what I'm asking is can you get an ebuild working? SRC_URI can be the project's download link, then if it works it's a lot less for a dev to do (ie just change SRC_URI which doesn't always happen, but I imagine would be sorted before it hit stable if not earlier, and whatever bug fixes come along.)
This works: % curl -o vcscommand.zip 'http://vim.sourceforge.net/scripts/download_script.php?src_id=7435' % unzip vcscommand.zip % mv vcscommand vcscommand-0.1_beta19 % tar cjf vcscommand-0.1_beta19.tar.bz2 vcscommand-0.1_beta19 < copy the tarball to distfiles, copy the ebuild & redigest >
vcscommand-0.1_beta19 is in CVS. Thanks for reporting ;)