Re: make dist

[Andreas Jaeger <aj@arthur.rhein-neckar.de>]

>>>>> Zack Weinberg writes:

 > I'm looking at a rewrite of make dist.  The goal is to reduce the amount of
 > magic, which should make Roland happy :)  I have in mind four make targets:

 > make dist - generate all generated files that go in the distribution.
 > This target is run for each subdirectory before making the tarfile.

 > make snap-dist - same as make dist, but for a snapshot release; this leaves
 > out info and compiled message catalogs, etc.

 > make release - call make dist, then wrap up a tarfile named suitably for a
 > release (libc-2.x.y.tar.gz).  If CVS is available, generate a patch also.

 > make snapshot - call make snap-dist, then wrap up a snapshot tarfile named
 > libc-YYMMDD.tar.gz (maybe YYYYMMDD?)  If CVS, make a patch.

I'd like to see (if Uli doesn't object because he's the one going to
use this mainly ;-) the following also added:
- make testrelease/prerelease to differentiate between a public
  release, a test release and a prerelease.  If make release could
  differentiate between them, it's also ok for me.
- README-alpha is always added except on public releases - there might 
  me other files (as you've mentioned already) which will only be
  distributed in some sets.
- make release/testrelease/prerelease/snap-dist should call `cvs tag'
  with the release number.

Please consider that the linuxthreads directory is an add-on
directory.  It's in the CVS tree but shouldn't be AFAIK put into
releases.

Andreas
-- 
 Andreas Jaeger   aj@arthur.rhein-neckar.de    jaeger@informatik.uni-kl.de
  for pgp-key finger ajaeger@alma.student.uni-kl.de