Re: Versioning of KVM

Baruch Even
2006-11-15T08:19:53Z

* Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org> [061115 10:00]:
> Baruch Even wrote:
>
>
> >>My current tree has fixes for most of the problems. I'll look at the clean targets (why are they necessary for packaging?)
> >>
> >
> >Some of the packages are being built by other computers, I'm building on
> >my machine only the i386 version and the amd64 is built by an
> >auto-builder. The clean target is needed since otherwise there are the
> >.d files which have absolute paths for my machine and my build
> >environment, this will kill the auto builder. In my case I build for
> >Debian testing on my machine and then use a chroot to do a clean build
> >for Debian unstable, the .d files killed the chroot build as well.
> >
> >The Debian build process does a clean before it starts the build to make
> >sure we do a pristine build every time to avoid such problems. It
> >doesn't always work when upstream clean target doesn't really clean.
> >Normally there is a clean target and distclean to really clean the
> >package back to distribution state.
> >
> >
>
> I don't understand. If you start from an empty directory and unpack the archive there, you shouldn't have any problems. I don't see how .d files can move from
> your machine to the autobuilder unless you added them to the archive.

You assume that I was able to do the change I needed in exactly one
take. The problem starts when there is an iterative process that only
after several tries you get to a working package. In that case there are
left overs from former builds, these left overs become part of the
Debian .diff.gz and are part of the Debian packaging.

Cheers,