FS#19164 - [vim] breakages introduced by new packaging
Attached to Project:
Arch Linux
Opened by Dave Reisner (falconindy) - Sunday, 18 April 2010, 22:28 GMT
Last edited by Dan Griffiths (Ghost1227) - Monday, 19 April 2010, 03:04 GMT
Opened by Dave Reisner (falconindy) - Sunday, 18 April 2010, 22:28 GMT
Last edited by Dan Griffiths (Ghost1227) - Monday, 19 April 2010, 03:04 GMT
|
Details
The new PKGBUILD for (g)vim has two issues:
1) GVim conflicts with Vim and vice versa. I understand that this was probably done to prevent upgrade issues, but it doesn't make practical sense. The inability to have both installed at the same time could leave users of gvim in a pickle should they not be able to get to X. 2) The previous package included a script -- fetch_runtime.sh, which did more than fetch the runtime. Due to it exclusion, syntax highlighting for PKGBUILDs (and some other pacman-related files) is missing. The script also appears to fetch a python completion file for Aaron. |
This task depends upon
Comment by Ionut Biru (wonder) -
Sunday, 18 April 2010, 23:22 GMT
i noticed myself that the syntax hightlight for PKGBUILD is broken
but i didn't investigated
Comment by
Dan Griffiths (Ghost1227) - Monday,
19 April 2010, 00:28 GMT
syntax highlighting for PKGBUILDs is indeed broken... we'll have
to fix that. however, the first issue you referenced is a
non-issue. i tested gvim installation without x and it works fine.
Comment by
Dave Reisner (falconindy) - Monday,
19 April 2010, 00:33 GMT
Fair enough -- I guess I misunderstood the previous bug report
that asked for the packaging change. I didn't realize it implied
that ncurses Vim was still present with the GVim package, but
you're indeed correct that item #1 is a non-issue. My apologies.
Comment by
Dan Griffiths (Ghost1227) - Monday,
19 April 2010, 02:35 GMT
Fixed in [testing]