[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: cvs development
> -----Original Message-----
> From: Grant Taylor [mailto:firstname.lastname@example.org]
> Sent: Wednesday, February 16, 2000 1:20 PM
> To: email@example.com
> Subject: Re: cvs development
> >>>>> Gregory Leblanc <GLeblanc@cu-portland.edu> writes:
> >> Right now, I have an unusual build procedure that involves
> a few Perl
> >> scripts, a database extraction, funky CVS checkout
> options, and so on.
> >> I'm not sure how this can fit in with a nightly build on metalab...
> > I don't follow you here. Can you tell me/show me what you
> are talking
> > about?
> My document has one section which is a summary of the support status
> for all the printers in my database. When I do a commit, the
> following happens:
> - A checkout happens with the -kv flag to get rid of the $..$ around
> the version and date.
> - A Perl program queries my SQL database and builds a linuxdoc-sgml
> summary of the contents.
> - Another Perl program preprocesses "src.sgml" into "pht.sgml"; this
> mainly consists of #including the database summary
> - All the usual sgml2foo stuff happens
> - The text one gets cat -s'ed to remove all those blank lines.
> - The built files are copied to my website.
> - The preprocessed pht.sgml file is mailed to the ldp and various
> - Everything in the build dir is blown away since it hasn't got $..$
> on the RCS id strings.
Ahh, yeah, I see. I guess that we probably need to define what kind of
processing will be done on documents in the CVS repository. I hadn't given
any thought to pre-processing, since I don't have a "need" for it right now,
nor time to figure it out. The only things that had ocured to me was the
processing of the SGML source into HTML/PS/PDF/Whatever. If we're going to
do pre-processing, especially if it will query an external database, then
things will be HUGELY more complex. Generating TOCs/Indexes from the SGML
source shouldn't be that dificult, but querying external datasources, hm...
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com