repository - How to get the latest gVim on Ubuntu 14.04? - Ask Ubuntu

this question has answer here:

• is there ppa gvim > 7.4.338? 3 answers

i create gvim appimage using packages 14.04 (why not 16.04? because 16.04 packages new appimages run on distributions newer or same age distribution who's packages they're built from). gvim appimage latest version of gvim, need repository 14.04 provides latest gvim. have searched launchpad vim ppas maintained , have not found (all ones found out-of-date).

my questions:

• i know can build latest gvim debian package checkinstall, want use gvim package repository build gvim appimage makes things lot simpler. where can find recent debian package of gvim?

• alternatively, how can build appimage container arbitrary set of binaries (downloaded somewhere or compiled source)?

an appimage self-mounting filesystem image contains application , needs run in single file.

here example builds gnu emacs on travis ci , packages appimage: https://github.com/probonopd/emacs.appimage

you should able to same gvim.

1. gather suitable binaries. if application has been compiled, can use existing binaries (for example, contained in .tar.gz, deb, or rpm archives). note binaries must not compiled on newer distributions ones targeting. in other words, if targeting ubuntu 9.10, should not use binaries compiled on ubuntu 10.04. upstream projects, might advantageous compile special builds use in appimages, recommend in case. see gnu emacs example above. (for re-using existing binaries, see https://github.com/probonopd/appimages/tree/master/recipes/meta instead.)
2. gather suitable binaries of dependencies not part of base operating systems targeting. example, if targeting ubuntu, fedora, , opensuse, need gather libraries , other dependencies app requires run not part of ubuntu, fedora, , opensuse in default installation.
3. create working appdir binaries. working appimage runs app when execute apprun file. again, see gnu emacs example linked above.
4. turn appdir appimage. compresses contents of appdir single, self-mounting , self-executable file. example above uses generate_type2_appimage function functions.sh this.
5. test appimage on base operating systems targeting. important step should not skip. subtle differences in distributions make must. while possible in cases create appimages run on various distributions, not come automatically, requires careful hand-tuning.

this sounds more complicated is, steps besides testing can done on 1 small bash script in example. can see @ https://github.com/probonopd/emacs.appimage, easy produce appimage.

i recommend work upstream authors of software, upstream project provide official appimage. way, upstream project can control end-to-end user experience of software; many upstream application projects appreciate. users can assured appimage put in way original authors of software intended , not changed in way intermediaries.