.cvsignore files

.cvsignore files

[Zefram]

-----BEGIN PGP SIGNED MESSAGE-----

The patch below adds a full complement of .cvsignore files.  These are
essential for those of us using CVS, and take up very little space.
They really should be included in the distribution because a significant
number of people need them and they really have to go into the repository
to be of full use.

 -zefram

      Index: .cvsignore
      *** /dev/null	Tue May  7 23:57:44 1996
      --- .cvsignore	Tue Apr 16 21:28:47 1996
      ***************
      *** 0 ****
      --- 1,9 ----
      + Makefile
      + config.cache
      + config.h
      + config.h.in
      + config.log
      + config.status
      + configure
      + stamp-h
      + stamp-h.in
      Index: Doc/.cvsignore
      *** /dev/null	Tue May  7 23:57:45 1996
      --- Doc/.cvsignore	Tue Apr 16 22:00:28 1996
      ***************
      *** 0 ****
      --- 1,3 ----
      + Makefile
      + *.[0-9]
      + *.[0-9]?
      Index: Etc/.cvsignore
      *** /dev/null	Tue May  7 23:57:47 1996
      --- Etc/.cvsignore	Tue Apr 16 21:28:52 1996
      ***************
      *** 0 ****
      --- 1 ----
      + Makefile
      Index: Functions/.cvsignore
      *** /dev/null	Tue May  7 23:57:48 1996
      --- Functions/.cvsignore	Tue Apr 16 21:28:52 1996
      ***************
      *** 0 ****
      --- 1 ----
      + Makefile
      Index: Misc/.cvsignore
      *** /dev/null	Tue May  7 23:57:48 1996
      --- Misc/.cvsignore	Tue Apr 16 21:28:53 1996
      ***************
      *** 0 ****
      --- 1 ----
      + Makefile
      Index: Src/.cvsignore
      *** /dev/null	Tue May  7 23:57:48 1996
      --- Src/.cvsignore	Tue Apr 16 21:28:54 1996
      ***************
      *** 0 ****
      --- 1,4 ----
      + Makefile
      + *.pro
      + zsh
      + signames.h
      Index: StartupFiles/.cvsignore
      *** /dev/null	Tue May  7 23:57:54 1996
      --- StartupFiles/.cvsignore	Tue Apr 16 21:28:55 1996
      ***************
      *** 0 ****
      --- 1 ----
      + Makefile
      Index: Util/.cvsignore
      *** /dev/null	Tue May  7 23:57:54 1996
      --- Util/.cvsignore	Tue Apr 16 21:28:56 1996
      ***************
      *** 0 ****
      --- 1 ----
      + Makefile

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBMY/zzXD/+HJTpU/hAQE1eAP/byzceIAU8sozyk4HuuMnYEVldC6Q7v+r
4wyaWX0ykgTqC1u+0Ot7hUW4xWvZg8XTOScHB8ku62LBhkgkztvUisKr8b/P0opl
T2Y7ONoAGUpIWWwbcOrp8/myaMhkF+Yoset//wm383cjvOjMcKpOerEG7CO8sJqD
WL3UfwuGMpY=
=oAGc
-----END PGP SIGNATURE-----

Re: .cvsignore files

[Zoltan Hidvegi]

> The patch below adds a full complement of .cvsignore files.  These are
> essential for those of us using CVS, and take up very little space.
> They really should be included in the distribution because a significant
> number of people need them and they really have to go into the repository
> to be of full use.

I do not think that this is really necessary.  I always build zsh in a
separate directory so the build process does not change anything in the
source tree with the exception of autoconf generated files.  Using
a separate build directory is always necessary in a multiplatform
environment.

If one uses a separate directory then only config.h.in, configure and
stamp-h.in remains.  But config.h.in, configure and the empty stamp-h.in
are archived in the RCS files.  This is necessary since the RCS file is
used to generate the patches between releases and not all people have
autoconf installed on their system.  And if a file is in the RCS
distribution it should not be put into .cvsignore.  After that no files
remained :-).

Zoltan

Re: .cvsignore files

[Zefram]

>I do not think that this is really necessary.  I always build zsh in a
>separate directory so the build process does not change anything in the
>source tree with the exception of autoconf generated files.  Using
>a separate build directory is always necessary in a multiplatform
>environment.

But not all of us do this.  I almost never use a separate directory.
We must at least allow for the possibility.

>If one uses a separate directory then only config.h.in, configure and
>stamp-h.in remains.  But config.h.in, configure and the empty stamp-h.in
>are archived in the RCS files.  This is necessary since the RCS file is
>used to generate the patches between releases and not all people have
>autoconf installed on their system.  And if a file is in the RCS
>distribution it should not be put into .cvsignore.  After that no files
>remained :-).

The way I use CVS, any file that can be generated (including
config.h.in and stamp-h.in) does not go into the repository.  In fact,
I do a "make superclean" before importing sources.  I find that this is
the best way to use CVS, as one doesn't end up with redundant diffs of
generated files.

-zefram