Graham Inggs <gra...@nerve.org.za> writes: > Thanks, that knocks about 30% off the size of the tarball. > > I should have been clearer in my first message. > Building with Debian's dh-autoreconf produces a list of unexpected > changes. These are normally a sign that the build did not clean up > properly. > When I built from CVS it detected that these files changed (were created), > but building from the source tarball did not show these errors, as the > generated files must have been identical to the provided files. > > I just wanted to make you aware of this, but it does not cause any problems > for me. > I can easily make exceptions for ufraw.1 and icons/ufraw_icons.h.
Users are not expected to run autoreconf. That's why the generated files are in the distfiles. I can understand why debian might want to run autoreconf (esp. if here is a patch to configure.ac), but it doesn't make sense to intentionally regenerate files and object to them being different. Is ufraw somehow special from the debian viewpoint? I would expect the exact same issue with many packges.
pgpxHWU55WpSR.pgp
Description: PGP signature
------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________ ufraw-devel mailing list ufraw-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ufraw-devel
