status of the thinkpad-source package

[Eduard Bloch]

#include <hallo.h>
* martin f krafft [Mon, Jul 31 2006, 03:55:53PM]:
> 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)

binary target is not for modules. binary-modules does build modules and
it does (usually) not run any clean rule. kdist_image does, though, with
multiple make calls so the dependency tracking is explicitely broken up.

> > 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?

No. All the time Debian maintainers have used the same changelog for
binary packages with different names. IIRC only the source package name
must match the one in changelog (not sure, though).

> > 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

You mean some rationale to explain _why_ the things are done this way?
Yeah, that maybe should be done. There are some docs about the
meta-framework but not much about makefiles. I though the comments
therein are self-explaining, mostly.

> 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.

You always need to understand basics.

> > I would call it collision of implementations.
> 
> Aha, that doesn't really mean a lot to me...
> 
> What do you suggest I do now?

For now? Comment all the changelog generating stuff. Define only
kdist_clean and binary-modules rules. Ping me in few days, I am too busy
these days, I may implement the m-a extension in the weekend. Then
create changelog.modules.in with the rewritting, the
changelog.modules.in would be generated when creating the -source
package.

Eduard.

-- 
<Knight5> hi - kennt jemand hier ein gutes, bebildertes howto um unter debian
	Samba als pdc zu konfigurieren?
<sirio> bebildert? wozu denn das?
<Knight5> fuer die Augen natuerlich ;-)