emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#19094: closed (Clean doc/{stamp-vti, version.texi}


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#19094: closed (Clean doc/{stamp-vti, version.texi})
Date: Fri, 21 Nov 2014 11:15:02 +0000

Your message dated Fri, 21 Nov 2014 12:14:05 +0100
with message-id <address@hidden>
and subject line Re: bug#19094: Clean doc/{stamp-vti,version.texi}
has caused the debbugs.gnu.org bug report #19094,
regarding Clean doc/{stamp-vti,version.texi}
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
19094: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=19094
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: Clean doc/{stamp-vti,version.texi} Date: Tue, 18 Nov 2014 15:35:43 +0100 User-agent: Mutt/1.5.23 (2014-03-12)
Hello,

Please, tell automake to clean doc/stamp-vti and doc/version.texi files.

I've come to this minor patch to make it possible to build the grep
debian package twice in a row (to build it over an already built
directory).

Thanks,

Santiago

Attachment: grep-doc-makefile-clean-files.patch
Description: Text Data


--- End Message ---
--- Begin Message --- Subject: Re: bug#19094: Clean doc/{stamp-vti,version.texi} Date: Fri, 21 Nov 2014 12:14:05 +0100 User-agent: Mutt/1.5.23 (2014-03-12)
El 18/11/14 a las 08:30, Eric Blake escribió:
> On 11/18/2014 07:35 AM, Santiago Ruano Rincón wrote:
> > Hello,
> > 
> > Please, tell automake to clean doc/stamp-vti and doc/version.texi files.
> > 
> 
> Sadly, this is not going to work.  These files are intentionally
> distributed as part of the tarball so that users don't have to have all
> the non-standard tools required to rebuild them; nuking them as part of
> 'make clean' would negate that benefit.  Nuking them during 'make
> maintainer-clean' would be okay, but doesn't automake already do that?
> 

make regenerates them. And yes, the problem is with the debian packaging
system, it doesn't like if changes in upstream sources are not included
in "known" patches. I've found a more debian suitable solution.

> > I've come to this minor patch to make it possible to build the grep
> > debian package twice in a row (to build it over an already built
> > directory).
> 
> What is the error you are seeing without this patch?  I'd rather fix the
> root cause than poke at symptoms.
> 
> >  EXTRA_DIST = grep.in.1
> > -CLEANFILES = grep.1 egrep.1 fgrep.1
> > +CLEANFILES = grep.1 egrep.1 fgrep.1 stamp-vti version.texi
> >  
> >  grep.1: grep.in.1
> >     $(AM_V_GEN)rm -f address@hidden $@
> > diff --git a/gnulib b/gnulib
> > index 46d015f..8415b67 160000
> > --- a/gnulib
> > +++ b/gnulib
> > @@ -1 +1 @@
> > -Subproject commit 46d015f9c3c959d2d9b9c3b9e9c99f3f420277b0
> > +Subproject commit 8415b6792e53f9aa309caedda799f9d9f3dffc53

Ouuch, I overlooked that!

Regards,

Santiago


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]