status of the thinkpad-source package

martin f krafft madduck at debian.org
Mon Jul 31 14:55:53 UTC 2006


also sprach Eduard Bloch <edi at gmx.de> [2006.07.31.1542 +0100]:
> > But let me ask why kdist_build bothers to call kdist_clean?
> 
> To make sure that no cruft is left over from a previous build.

Well, I am not sure this is actually the task of m-a, is it? I mean,
sure, if it's actually being called as m-a (dpkg-buildpackage also
calls clean), but not if i invoke the rules directly (fakeroot
debian/rules binary does not call clean)

> Generaly it is an easy task unless you try to integrate some own
> implementation over the provided stuff. And changelog
> modifications have not been "supported" yet, though I see that it
> sometimes make sense to look at when the package has been build
> and by whom.

Well, also, you *need* to change the package name in the changelog,
right?

> > I wish someone were to show me how to properly create -modules
> > packages. I wish there were some document out there that would
> > explain it once and for all.
> 
> The current dh-make templates do that, or see "templates"
> directory shipped with m-a somewhere. As said, changelog
> modifications do not work well, I think the extra vars you
> requested should be added there. Then you can have
> a "changelog.modules.in" which is used to cook debian/changelog.

Well, templates are not documentation. I appreciate that there are
templates that will help me make things work, but I'd much rather
understand what's going on, and I think that's what should be the
primary goal. Templates are useful, but only after you've understood
the basics. Otherwise we'll end up with hacks and complex,
non-working stuff like my work on thinkpad.

> > > Eg.  what is a changelog good for if it does not document
> > > changes? (unlike the source' package changelog).
> > 
> > The changelog documents a change, namely that the package was
> > transformed from -source to the -modules package. This is
> > a required step, isn't it?
> 
> Is it? I don't see it that way, somehow.

Uh, dh_builddeb uses dpkg-parsechangelog for most of the information
it gathers... as do many other tools.

> > Or what exactly am I doing wrong?
> 
> I would call it collision of implementations.

Aha, that doesn't really mean a lot to me...

What do you suggest I do now?

-- 
 .''`.     martin f. krafft <madduck at debian.org>
: :'  :    proud Debian developer and author: http://debiansystem.info
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
this space intentionally left occupied.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature (GPG/PGP)
Url : http://lists.alioth.debian.org/pipermail/pkg-tpctl-devel/attachments/20060731/8cd88364/attachment.pgp


More information about the pkg-tpctl-devel mailing list