On Sun, Oct 27, 2019 at 4:37 PM Sihera Andre <[email protected]> wrote: > > Hi Dominique, > > > On 26/10/2019 19:10, Dominique Pellé wrote: > > Sihera Andre <[email protected]> wrote: > > > >> 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. > > > > Never install things in /usr/bin/ > > Files there are managed by Ubuntu packages. > > Thank you for the advice. I am aware of the risks > of putting files directly in /usr/bin. > > As far as I was aware, I didn't know you don't actually > released "vim.huge" into the official repositories, so I > assumed I was free to do so. > > Do you release "vim.huge" into the official repositories?
The same sources are good for all featuresets depending on how you set configure arguments. I'll attach the configure parameters I use myself. Don't forget to change at least the "compiled by" line (and possibly other params to suit you) and see http://users.skynet.be/antoine.mechelynck/vim/compunix.htm about how to use them. The build I use day-in day-out is the "big" one but I compile all 5 as a sanity check and from time to time I check some detail on one of the 4 other builds. When there is a change to the sources, I compile them all in parallel (without the make program's -j switch) in 5 different shells each with its own set of environment settings and each in a different shadow directory. (About how to make shadow directories, see the "shadow" target in the src/Makefile and the -e switch to "make".) > > > > > Instead, you should install vim in /usr/local/bin. > > > > If you just do... > > > > $ ./configure --with-features=huge > > $ make -j8 > > $ sudo make install > > You know what would be *really* useful? If you could > provide a "make uninstall" that put my /usr/local/share > and /usr/share/vim back to the exact state before I > did "make install". > > Then I wouldn't have to use "git" to manage it all > myself when it goes wrong. > > > Cheers, > > Andre. > > > > Then vim will be installed in /usr/local (including binary > > in /usr/local/bin and runtime in /usr/local/share/...) so > > everything will be consistent, and it won't interfere with > > Ubuntu packages. > > > > Make sure /usr/local/bin is in your path before /usr/bin > > to run your own version of Vim rather than the Ubuntu Vim. > > > > Regards > > Dominique Best regards, Tony. -- -- 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/CAJkCKXsrX0HkuOMrpgkDD0tE%2BSnTAFAo63%2Bq1a9qWkyejrtxVw%40mail.gmail.com.
bigcfg
Description: Binary data
normcfg
Description: Binary data
tinycfg
Description: Binary data
smallcfg
Description: Binary data
hugecfg
Description: Binary data
