Hi Christian,
On 25/10/2019 17:53, Christian Brabandt wrote: > On Fr, 25 Okt 2019, Sihera Andre wrote: > >> The reason I don't "simply" do "make install" is because, in the past, >> what was installed from a locally checked-out repository and what was >> shipped with the operating system package manager (in this case, Ubuntu) >> often did not match even if I made sure to check out the same version >> (or slightly newer) as the repository package versions. >> >> I got tired a long time ago of typing "make install" on a number of >> projects (not just ViM) just to have everything stop working as they >> destroyed the environment that the OS package manager was doing a very >> good job of maintaining. I ended up then (and still do now) using git to >> version control a good proportion of my /usr/local and /usr/share settings >> just so that when I do a "make install" on a locally-built package and >> everything stops working I can simply just do a "git checkout" to bring >> it all back. >> >> When I build a new OS (which, incidentally, is only once every three to >> five years), I just want to grab the runtime from the official OS >> repository (Ubuntu), then checkout the source code so I can build the >> "huge" version of the ViM binary with a specific patch for "ctags" which >> ViM still hasn't supported for as long as I can remember (10? 15 years? >> but that's a different story), then I just substitute vim.tiny in /usr/bin >> for vim.huge, same version, no fuss, and that should be it for another >> five years. >> >> It may be not your preferred way of doing it, but then environment >> stability and continuity of features across upgrades are my top concerns. >> >> Anyway, the original problem with "matchparen.vim" is solved, and the root >> cause is known, so I thank you for your time. > Understood. However note that this is asking for trouble sooner or > later. With all due respect... When the official distribution for an OS has runtime version "X" (for example, 8.0.1766) and I then "git clone" the ViM source repository and "git checkout X" to build a binary, and the subsequently built binary, which I should just be able to drop on top of "vim.tiny", is not compatible with version "X" of the runtime, then I think it is not me who should be looking at their build procedures, or version number management for that matter. > <snip> > > I personally also compile my own version using a custom --prefix= > argument to the ./configure files. Then when running make install, those > files do not interfere with the packaged vim-runtime files (and I can > even use either my self-compiled vim binary or the system provided vim, > depending on the path). > > Best, > Christian It's refreshing to see that we're all quite similar :-) If "make install" is dependable, I may yet get it another try. Again, thanks for your assistance. Cheers, Andre -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/PSXP216MB027795C0FA665824AC297F38C0650%40PSXP216MB0277.KORP216.PROD.OUTLOOK.COM.
