Thanks!
On Fri, 2013-01-18 at 20:35 +0100, Kern Sibbald wrote:
> Hello Willem,
>
> After looking at the Makefiles, it does look like a make clean
> will do a reasonable job of cleaning up files. Hopefully
> I will be making a new release in a few weeks and when I do
> so, I will try the "make cl
Hello Willem,
After looking at the Makefiles, it does look like a make clean
will do a reasonable job of cleaning up files. Hopefully
I will be making a new release in a few weeks and when I do
so, I will try the "make clean", if that does not work, I will
remove the config.log and config.status
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 b
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 dire
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?
G
