On Fri, 2007-05-04 at 21:02 -0500, Manoj Srivastava wrote: > Well. I think I want to make a) work here as well. So, one thing > I can do is if $(SHELL /bin/sh scripts/setlocalversion) is not null, > then append -dirty to it (since make-kpkg does make changes to the > Makefile there, so ./debian is not nuked during dpkg-buildpackage). > > I think this might work.
Why not simply make the changes before control/changelog are generated? That way, -dirty will be present automatically. > Well. This is a shortcoming I want to solve. You see, with all > the localversion addenda possible now, and with the possibility someone > will come up with other ways to much with version numbers, I wanted to > just run make to determine what the localversion was. Ah. I'm beginning to understand the issue here. You could do as I said above, but then somebody could reconfigure the kernel and add a localversion in the config which would screw up make-kpkg again. Hmm. It seems that ought to be a clear case of "don't do that then". Or actually, since make-kpkg requires that you configure the kernel before running it, it'd actually work to do the changes to scripts/ before generating control and changelog. Actually, what's wrong with simply re-generating the changelog/control files all the time and accepting whatever the kernel build process thinks the version is? johannes
signature.asc
Description: This is a digitally signed message part
