Tony Mechelynck, 2010-05-28 02:59:
> On 28/05/10 01:54, Markus Heidelberg wrote:
> > You can still add something like .*.swp to .hgignore for the swap files.
>
> I would add not only .*.swp but even .*.sw? (to ignore .swo .swn etc.),
Yes, that would make sense.
> src/auto/config.mk (which is regenerated by configure from the
> config.mk.dist and a couple of others) and runtime/doc/tags (which is
> regenerated by make install).
But since these files are tracked by hg, you cannot ignore them. It's
annoying that the worktree is dirty after each "make install".
Automatically generated files shouldn't be tracked. In the git
repository I removed src/auto/config.mk because of this, but apparently
it is needed in some situations. In .hgignore there is the comment "We
do need src/auto/configure and src/auto/config.mk."
> However, maybe I'm talking from a
> "provincial" Linux standpoint: I'm fairly certain that users of
> makefiles other than Makefile don't need src/auto/config.mk but what
> about the help tags? I guess all makefiles "ought" to rebuild them at
> some point but do they?
I think the same and then the file could be deleted from the repository.
I guess it's included for people to update the runtime files from the
ftp server without doing "make install". Bram, do you continue to
support the ftp/rsync access for the runtime files? But runtime/doc/tags
could still be shipped via ftp, even if it's deleted in hg.
> Ah, and shadow directories. In theory they can be named anything (below
> src/ ) but the default is src/shadow and I propose to also "ignore"
> src/shadow-* in case someone had several shadow directories -- with a
> notice somewhere (maybe as a comment in either or both of the
> src/Makefile and .hgignore) that shadow-<something> is the preferred
> name.
I think we should stick to the defaults from the Makefiles to not
pollute the .hgignore too much. The next person wants to have the shadow
directory in src/.shadow or so. There are even opinions to only include
the files from the build process into the ignore rules and not include
something like *~ .*.sw? *.rej *.orig, which is dependent on personal
use. But it makes at least sense to ignore files generated by Vim in
Vim's repository. It's still possible to extend the ignore list in the
local clone, for example:
.hg/hgrc:
[ui]
ignore = ~/.hgignore-for-vim
> What have we forgotten? Ah yes, src/auto/if_perl.c (on Linux) and
> src/if_perl.c (on Windows). Is that all now?
This is the .gitignore from the git repository:
*.swp
*.exe
*.obj
*.dll
*.pdb
*.RES
*.exp
*.ilk
cscope.*
tags
/src/pathdef.c
/src/types.vim
/src/vim
/src/objects/
/src/obj*/
/src/gobj*/
/src/ObjG*/
/src/ObjC*/
# Automatically changed/filled files, shipped with Vim with minimal content.
# Deleted in this repository, otherwise this rules would have no effect.
/src/auto/config.h
/src/auto/config.mk
/src/auto/config.cache
/src/auto/config.log
/src/auto/config.status
/src/auto/if_perl.c
/src/auto/link.log
/src/auto/link.sed
/src/auto/osdef.h
/src/auto/pathdef.c
/src/po/*.ck
/src/po/*.mo
/src/po/sjiscorr
/src/testdir/test*.out
/src/testdir/small.vim
/src/testdir/tiny.vim
/src/testdir/mbyte.vim
/src/testdir/test.log
/src/xxd/xxd
/src/GvimExt/gvimext.dll
/src/GvimExt/gvimext.lib
/src/GvimExt/gvimext.o
/src/GvimExt/gvimext.res
--
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
