Re: [Freeciv-Dev] CVS: dwp: Autogenerated files from previous batch of chan...

[Mitch Davis <mjd@xxxxxxxxxx>]

Falk Hueffner wrote:
> 
> freeciv@xxxxxxxxxxxxxxxxxxxxxxxx writes:
> 
> > This is an automated notification of a change to freeciv cvs,
> > on Sat Nov 14 17:53:15 PST 1998 = Sun Nov 15 01:53:15 1998 (GMT)
> > by David Pfitzner <dwp@xxxxxxxxxxxxxx>
> >
> > ---- Log message:
> >
> > Autogenerated files from previous batch of changes:
> > aclocal ; autoheader ; automake ; autoconf
> 
> Are you folks sure it is a wise idea to have autogenerated files in
> the CVS tree? They're at best redundant, and at worse outdated.

After thinking about this for a bit, I'm now leaning towards
having a "developer's kit".  A developer's kit would contain
all the generated files, in case people don't have the means
to regenerate them.

David made a valid point that only a few people have access
to change the originals, and if we stress that these people
also have the responsibility to keep the autogenerated files
up-to-date, then I think this answers your point.

Would it be feasible to include _no_ autogenerated files in
the release, except for configure?  I think the only people
who need them are developers or package maintainers.

The developers kit would also contain the configuration files
for each of the distributions that wanted to have package
files; the debian dir comes to mind...

One other benefit:  We could release the developer's kit
a day or two after the main release, thus giving package
maintainers a chance to get things in order.

Just a thought...

Regards,

Mitch.
--
| mailto:mjd@xxxxxxxxxx       | Not the official view of: |
| mailto:mjd@xxxxxxxxxxxxxxxx | Australian Calculator Opn |
| Certified Linux Evangelist! | Hewlett Packard Australia |