quilt-dev
[Top][All Lists]
Advanced

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

[Quilt-dev] Re: quilt Makefile


From: Martin Quinson
Subject: [Quilt-dev] Re: quilt Makefile
Date: Thu, 30 Jan 2003 10:10:07 +0100
User-agent: Mutt/1.4i

Moved back to the ML for archiving ;)

On Wed, Jan 29, 2003 at 06:13:23PM +0100, Andreas Gruenbacher wrote:
> Hi Martin,
> 
> you may want to add those files in debian/ that should be distributed to 
> the $(SRC) in the Makefile, so that `make dist' does the right thing. 
> Currently the debian files are not being packaged. Something like this 
> should do.
> 
>       --- Makefile    29 Jan 2003 16:42:19 -0000      1.5
>       +++ Makefile    29 Jan 2003 17:09:37 -0000
>       @@ -46,6 +46,10 @@
>        DIRT +=                $(DOC_IN)
>       
>        MAN1 :=                bin/guards.1
>       +
>       +DEBIAN :=      control copyright docs manpage.sgml.ex \
>                       prerm rules watch
>       +SRC +=         $(DEBIAN:%=debian/%)
>       +
>  
> #-----------------------------------------------------------------------

Thanks, I did that, just removing manpage.sgml.ex, which is an unmodified
template and don't need to go in tarballs, and the watch file, which is used
to track new version of upstream, since for quilt, upstream and debian
version are quite the same. 

> Also what do you think of a single changelog? I am currently generating 
> the RPM changelog from rpm.changes; inside SuSE we keep the change logs 
> in such .changes files. But I have noticed that there is a separate 
> changelog in debian/.

Mmm. No, that's needed by debian tools. dpkg-buildpackage parse this file to
check what the version number is. So, if you want to use quilt.changes,
you'll have to format this file using the debian-changelog-mode from emacs
(or the vim version, or mimic the format). Then, you'll have to put a link
from quilt.changes to debian/changelog, which is the location looked by tools.

But there is no conflict between the two changelogs. quilt.changes should
document changes to source code while debian/changelog should document
debian packaging changes (like the recent change from architecture: all to
architecture: any due to the C program we now use).

You can see that the 0.11 debian/changelog's entry speaks a bit about
upstream changes, but that's only because we didn't have any upstream
changelog at this time.

Thanks, Mt.

-- 
This message has been made up using recycled ideas and language constructs.
No tree has been cut nor animal harmed in process of making it.




reply via email to

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