Re: Build managment with Delta-V
Rodent of Unusual Size (Ken.Coar@Golux.Com)
Thu, 29 Jul 1999 06:27:02 -0400
Message-ID: <37A02C76.277A74D@Golux.Com>
Date: Thu, 29 Jul 1999 06:27:02 -0400
From: Rodent of Unusual Size <Ken.Coar@Golux.Com>
To: Jim Whitehead <ejw@ics.uci.edu>
CC: ietf-dav-versioning@w3.org
Subject: Re: Build managment with Delta-V
Jim Whitehead wrote:
>
> 2) source code remote, compiler remote, object files remote
>
> In this model, you would submit the URL of a makefile, some
> parameters, and a workspace to a remote build server, and the build
> server would then go off and remotely compile the source code.
In ye olden daze (before the onset of ye greye haires), this was
called 'batch processing.' Compared to one of its successors,
interactive development, it was *not* fun. You ask how I imagine
building? This option is not one I care to imagine.. been there,
done that, dropped my obligatory box o' cards.
You seem to be equating 'compile results' with 'object files,'
which I think is a bit restrictive. I can envision cases
in which the compilation output should go into SCM (such as
a 'compilation' of configure.in, resulting in configure, which
goes back into SCM; or perhaps the output from a 'make depend').
I like the CVS model, which would have me replicate the source
to my workspace, perform the build, and then check in any
updated results as appropriate. I'm not in favour of any
remote processing at all, unless features or functions are
required that cannot exist locally.
--
#ken P-)}
Ken Coar <http://Web.Golux.Com/coar/>
Apache Software Foundation <http://www.apache.org/>
"Apache Server for Dummies" <http://ASFD.MeepZor.Com/>