Reply to message «Re: 7.3 missing File Browser ??», sent 22:06:51 07 November 2010, Sunday by Benjamin R. Haskell:
> Just because you *can* do that doesn't mean you should. This is bad > advice, especially if you want to do any development on Vim. It's bad > for the same reason modifying files under VIMRUNTIME is bad: there are > cleaner mechanisms for making local customizations. And it's bad from a > development standpoint because you end up with modified files in the > source directory that the version control system doesn't know *should* > be modified. Both of these can cause problems when you update your > source files (unless you immediately rebuild). Where have you seen modified files in source directory? I do not modify anything in $VIMRUNTIME, I just do not install vim anywhere. If you are talking about files that are generated by `make', then there are two points: 1) make does not modify any tracked files (configure does); 2) you cannot install vim without building it while inside a repository. > In general, version control systems (in this case Mercurial) and build > systems (in this case autotools) aren't set up to cleanly handle the > case where source, build, and installation directories are the same. You do not need any setup, you just should not track new files. .hgignore in vim repository already has lines that handle it. > Much better is to simply specify a prefix argument when you run > `configure`, e.g.: > > ./configure --prefix=$HOME/myvim --whatever-other-features It is not better because it affects only make install. But before you install you must build it. And, surprise, configure will modify src/auto/config.mk which is tracked. > If you specify a directory to which you can write files, you don't need > root privileges for `make install`. I know.
signature.asc
Description: This is a digitally signed message part.
