How about a nightly build which encompasses these missing files? Those pulling 
svn could just "live with it"? I've just been using svn (to get around the 
pcre_exec bug) and copying the binaries to where I need them manually.

> -----Original Message-----
> From: bug-cfengine-bounces+jmacfarland=nexatech....@cfengine.org
> [mailto:bug-cfengine-bounces+jmacfarland=nexatech....@cfengine.org] On
> Behalf Of Mark Burgess
> Sent: Tuesday, May 19, 2009 4:49 AM
> To: Faehl, Chris
> Cc: bug-cfengine@cfengine.org
> Subject: Re: texinfo/info files missing from svn
> 
> 
> Hi Chris, I need to figure something out here. The actual document
> source is made up of hundreds of small files that are integrated by
> cf-know. I'll look through this and fix it somehow soon.
> 
> M
> 
> Faehl, Chris wrote:
> > Several doc files (man and info/texinfo) are missing in SVN – even
> the
> > 3.0.1 tag – that are distributed in the 3.0.1 release tarball. This
> > causes the build to fail in docs for fresh SVN trees.  For
> completeness,
> > I list all file differences between the 3.0.1. release and the SVN
> > repository.
> >
> >
> >
> > diff cfengine-3.0.1/docs cfengine-svn/trunk/docs
> >
> > Only in cfengine-svn/trunk/docs: add_modules.html
> >
> > Only in cfengine-svn/trunk/docs: agents.html
> >
> > Only in cfengine-svn/trunk/docs: cf3.html
> >
> > Only in cfengine-3.0.1/docs: cf3-reference.info
> >
> > Only in cfengine-3.0.1/docs: cf3-reference.info-1
> >
> > Only in cfengine-3.0.1/docs: cf3-reference.info-2
> >
> > Only in cfengine-3.0.1/docs: cf3-Reference.pdf
> >
> > Only in cfengine-3.0.1/docs: cf3-Reference.texinfo
> >
> > Only in cfengine-svn/trunk/docs: cf3_variables.html
> >
> > Only in cfengine-3.0.1/docs: cf-agent.8
> >
> > Only in cfengine-3.0.1/docs: cf-execd.8
> >
> > Only in cfengine-3.0.1/docs: cf-key.8
> >
> > Only in cfengine-3.0.1/docs: cf-know.8
> >
> > Only in cfengine-3.0.1/docs: cf-monitord.8
> >
> > Only in cfengine-3.0.1/docs: cf-promise.8
> >
> > Only in cfengine-3.0.1/docs: cf-promises.8
> >
> > Only in cfengine-3.0.1/docs: cf-report.8
> >
> > Only in cfengine-3.0.1/docs: cf-runagent.8
> >
> > Only in cfengine-3.0.1/docs: cf-serverd.8
> >
> > Only in cfengine-svn/trunk/docs: CollectingDefinitions.html
> >
> > Only in cfengine-3.0.1/docs: ContributorStatement.pdf
> >
> > Only in cfengine-svn/trunk/docs: ConvergenceAndForcedChanges.html
> >
> > Only in cfengine-svn/trunk/docs: filelogic.html
> >
> > Only in cfengine-svn/trunk/docs: list_expand.fig
> >
> > Only in cfengine-svn/trunk/docs: Makefile
> >
> > Only in cfengine-svn/trunk/docs: modus_operandi.html
> >
> > Only in cfengine-svn/trunk/docs: ProcessesExecution.html
> >
> > Only in cfengine-svn/trunk/docs: syntax.html
> >
> > Only in cfengine-svn/trunk/docs: texinfo.log
> >
> >
> >
> > What’re your thoughts on the existence of these files, Mark? Moving
> man
> > pages and the cf3-Reference.texinfo will get you most of the way
> there,
> > but introduces additional build dependencies. Alternately, could
> modify
> > the Makefile to remove the doc targets (or make the docs  an optional
> > build), or could check in the target doc files into SVN.
> >
> > --
> >
> > Chris Faehl
> >
> > Hosting Engineering Systems Manager, RightNow Technologies
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> ---
> >
> > _______________________________________________
> > Bug-cfengine mailing list
> > Bug-cfengine@cfengine.org
> > https://cfengine.org/mailman/listinfo/bug-cfengine
> 
> --
> Mark Burgess
> 
> -------------------------------------------------
> Professor of Network and System Administration
> Oslo University College, Norway
> 
> Personal Web: http://www.iu.hio.no/~mark
> Office Telf : +47 22453272
> -------------------------------------------------
> _______________________________________________
> Bug-cfengine mailing list
> Bug-cfengine@cfengine.org
> https://cfengine.org/mailman/listinfo/bug-cfengine

_______________________________________________
Bug-cfengine mailing list
Bug-cfengine@cfengine.org
https://cfengine.org/mailman/listinfo/bug-cfengine

Reply via email to