status of the thinkpad-source package

[Eduard Bloch]

#include <hallo.h>
* martin f krafft [Sun, Jul 30 2006, 11:47:17PM]:

> > What should it be good for? Every time one of the files change,
> > configure-stamp shall ge generated? Ok, but if none of them changes and
> > package is just rebuilt?
> 
> I only use the make syntax for implcitly ensure that these files are
> processed. I don't expect them to change. I expect the configure
> target to be rerun because configure-stamp vanished.
> 
> But I understand now what you are saying: I expected
> a missing configure-stamp to remake the debian/control file, which
> obviously won't happen unless debian/control.in changed.
> 
> I'll fix that.

Another idea I had... why not using targets like
configure-$(KVERS)-stamp and removing *stamp in the clean rules? Not
sure how that would work, though.

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

> > I do not see what this hocus pocus should be good for. Sorry,
> > guys, I do not like what you do (or someone did before you).
> > I suggest you make the stuff work FIRST and then reconsider what
> > cosmetic changes are good for _before_ doing them.
> 
> I don't know what you're trying to say. I am simply trying to make
> thinkpad-source work with module-assistant, and it's proven to be
> a massively difficult task. I could not find any proper
> documentation or HOWTO, so I had to look at what other packages are
> doing, and it's mostly just hacks all over the place.

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.

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

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

> Or what exactly am I doing wrong?

I would call it collision of implementations.

Eduard.

-- 
<Treibholz> hmm, den gmx-smtp kann man wohl nicht als relay verwenden...
<Treibholz> geht das mit dem von web.de?
<Salz> Treibholz: ohne authentifizierung eh nicht
<Treibholz> Salz: ich poppe alle 10 Minuten
<Salz> .oO(neid)