Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#6990 - vim and gvim too frequent updates: is it possible to split?
Attached to Project:
Arch Linux
Opened by Giorgio Lando (patroclo7) - Tuesday, 24 April 2007, 10:08 GMT
Last edited by Tobias Kieslich (tobias) - Sunday, 29 April 2007, 00:45 GMT
Opened by Giorgio Lando (patroclo7) - Tuesday, 24 April 2007, 10:08 GMT
Last edited by Tobias Kieslich (tobias) - Sunday, 29 April 2007, 00:45 GMT
|
DetailsThe vim and gvim packages are very often updated to development versions, such as the actual 7.0.224. I did not notice any serious instability, but I wonder if this choice can cause instabilities in the future. Wouldn't it be better to stay with 7.0 (the latest stable version, according to www.vim.org) in current and to push those frequent updates in unstable, naming them vim-unstable and gvim-unstable?
|
This task depends upon
The frequent updates shouldn't make you believe that vim actually is an unstable version, I just keep it uptodate when I have the time to do so.
I just try to make it not every patch since the down and upload becomes to much. So I wait for important stuff or a reasonable timespan.