Re: [CVS] commit

Date view Thread view Subject view Author view

From: Archie Cobbs (archie@whistle.com)
Date: Thu Sep 10 1998 - 13:26:03 EDT


Godmar Back writes:
> > Now I understand the implicit assumptions you're referring to.
> > However, does it make sense to *not* do it this way? That is,
> > if your purpose is to regenerate derived files so you can
> >
> > (a) Check them in, or
> > (b) Create a tarball
> >
> > then you would want to do this inside the source tree. The main
> > motivation for "make derived-files" is for a developer to update
> > all of the *source* files that are derived from other source files.
>
> I never configure in my source tree, and I don't see why I should
> be required to start doing that for derived files.
>
> I think we got feedback from the mailing list that was in favor of
> having a complete environment available via CVS, so let's respect that.

I heard that feedback also, but personally I just disagree.
I mean, if you want to do development, and you're starting
from scratch, all you have to do is install kaffe-snap (it's
very easy), and then cvs update. So I don't quite understand
why people need derived files in the *repository* so bad.
But maybe I'm missing something.

> For instance, I checked out japhar. They don't even have a configure
> file in their CVS. The result: it doesn't work (aclocal fails), despite
> the fact that I have the required versions of automake and autoconf
> installed. So much for that piece of GNU wonderware. I sent them
> mail asking about it.

Yeah, that sounds like a lousy experience, but to me it means
"there's a bug" more than "the model is broken".

This is mostly of theoretical interest to me. My only point is a
theoretical one, ie, that a source code repository has a certain
purpose, and a distribution tarball has a different purpose. Mixing
them just confuses things and leads to potential inconsistencies.

> Actually, if we assume for a moment that we do have a compatible
> Klasses.jar file in the CVS repository, then we should be able to first
> build kaffeh, and then create the derived header files. This would avoid
> the need of having them in CVS.

Yeah, that at least we could do.

-Archie

___________________________________________________________________________
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com


Date view Thread view Subject view Author view

This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:56:56 EDT