latexsuite is a very handy extension for vim. Yet it has seen little attention from ebuild maintainers as the current (old) version 1.5.20060325 shows and some features appear to be broken. Though upstream has not released a new revision, they still seem to work on it (http://sourceforge.net/projects/vim-latex/files/ with newest snapshot being vim-latex-1.5-20091002-r1074.tar.gz) Could you add an ebuild using one of the snapshots? Reproducible: Always
OK, probably time to update it then. At some point fairly recently I had discussed this with a dev and we decided against an update until an upstream release, but if there's a demand for it there's no reason it can't go ahead. I'll do some testing with the latest snapshot.
Created attachment 207693 [details] latexsuite-1.5.20091002.ebuild New ebuild version requested for upstream snapshot 1.5-20091002-r1074 Checked for new regressions upstream. There are a few debian patches on: http://sourceforge.net/mailarchive/forum.php?thread_name=1252956121.12038.57.camel%40LAPJFS&forum_name=vim-latex-devel Unfortunately the link on that page is dead. I didn't look into it any further than that. Let me know if there are any problems.
bug 289890 is for renaming this package from latexsuite to vim-latex It will be reopened once this bug is closed.
Created attachment 211460 [details] latexsuite-1.5.20091002.ebuild Added extra post-merge text that makes the plugin load for .tex files in vim7, otherwise it can be quite confusing for the user to work out why it isn't working. Should be harmless in vim6.
Created attachment 217086 [details] Version bump Version bump to vim-latex-1.8.23-20091230-r1079. Only renamed the ebuild, changed the revision number and the version separator.
Adding to cc list :)
Ebuild works as =app-vim/latexsuite-1.8.23.20100129 (MY_REV=1104) This has been the most-recent snapshot for 7 months, it's probably as close to a release as we're going to get for the foreseeable future.
I've added a version bump for the upstream snapshot 1.8.23-20100129-r1104 to the tree. I'll reopen bug #289890 to get the package renamed as well.
