Re: Dependencies on shared libs, take 2
* Raphael Hertzog (firstname.lastname@example.org) [070618 11:36]:
> On Mon, 18 Jun 2007, Mike Hommey wrote:
> > > The generated file is updated... and the file in the source package
> > > doesn't need to be updated so often. Additionnaly you can avoid having to
> > > rebuild once knowing that it will fail... let the build update the
> > > generated file, get the diff from the build log and commit it in your
> > > repository so that it will be used for the next upload.
> > >
> > > If your build is rather large, it can make sense.
> > No, it doesn't. Files in the debian/ directory should not be modified
> > during the build. The correct file should already be in the .diff.gz.
> The file in debian is *not* updated, that's precisely the point of this
> discussion. Joss wants the maintainer to update it beforehand, I let the
> maintainer update it after its final build but it will then be used only
> for the next upload of course. (The file in debian is not auto-updated
> during the build in any case)
But that is *wrong* in my opinion. Please make sure that the source
package contains all the information it needs, at least for libraries.
> The file in in the binary package (debian/<package>/DEBIAN/symbols) is
> however generated at build time (and has thus updated symbol information).
If it is not part of the source package, it is not guranteed to be
updated with the next build either.