Hi,

I download the bacula-doc tarball from sourceforge. 
https://sourceforge.net/projects/bacula/files/bacula/5.2.6/

This I import whit 'git-import-origin' into the debian git.
After this import both config.log and config.status files are in the
repository.
The only way to remove it is to untar bacula-doc, remove both files, tar
it and then import it. However this is not a standard Debian procedure
[1] and 
sometimes this breaks the automatic build process.

Perhaps a make clean after your 'build documents' step is a possibility
to remove both files.

[1] http://wiki.debian.org/IntroDebianPackaging

Greetings,
Willem

On Fri, 2013-01-18 at 17:27 +0100, Kern Sibbald wrote:
> Hello,
> 
> Hmm. That is an interesting question that is not so easy
> to answer.  The process we use for releasing the bacula-doc
> tar file is:
> - git archive --format=tar ...
> - detar the document directory
> - configure the manual (must run ./configure ...)
> - build the documents
> - re-tar the document directory
> 
> So, we end up with a fully "pre-built" set of documents (or at least
> in English) in pdf and html format, because some users find it 
> difficult to get the zillion dependencies of LaTeX setup correctly.
> 
> So, the real question is are you building everything from scratch,
> in which case you should start with the original git archive
> file, which is clean.  If you want the English docs built, there there
> are a *lot* of files that do not make up the "source" code.
> 
> If you want a clean set of files, it would probably be best
> for you to pull the archive yourself directly from the
> Bacula public repo using the tag we setup.  We can,
> of course, remove the two files before re-tarring everything, but
> as I say that leaves a lot of other temp files (lots of .log, ...) in
> the tar file.
> 
> Could you let me know a bit more what you would like based on the
> above?  Then I can figure out exactly how to do what will work the
> best.  For me, it is rather trivial to remove the two files in
> question 
> before re-tarring the file, otherwise I can give you the details of
> the git command needed and the release tags.
> 
> Best regards,
> Kern
> 
> 
> On 01/18/2013 04:38 PM, W. van den Akker wrote:
> 
> > 
> > Hi,
> > 
> > We are currently migrating the bacula-doc 5.2.6 into debian.
> > 
> > The upstream tarball contains the files config.log and
> > config.status.
> > This breaks the default build process and we have to remove it.
> > 
> > Is it possible to remove these files from the barcula-doc tarball,
> > starting
> > from 5.2.13 or so?
> > 
> > Greetings,
> > Willem vd Akker 
> > 
> > 
> > ------------------------------------------------------------------------------
> > Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and
> > much more. Get web development skills now with LearnDevNow -
> > 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
> > SALE $99.99 this month only -- learn more at:
> > http://p.sf.net/sfu/learnmore_122812
> > 
> > 
> > 
> > 
> > _______________________________________________
> > Bacula-devel mailing list
> > Bacula-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bacula-devel
> 
> 


------------------------------------------------------------------------------
Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and
much more. Get web development skills now with LearnDevNow -
350+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122812
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel

Reply via email to