At 12:31 Uhr +0100 03.04.2002, Damian Steer wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >Hi, > >I've just had a report of a build error (for amaya-5.3-2) which I've >been unable to to reproduce. (No idea why it won't build, but that's >not relevant here). > >I think I've solved it with a minor change to the patch file, but my >question is - should it now be amaya-5.3-3? > >It seems the right thing to do, however for all those people who never >experienced the problem it will mean an unnecessary rebuild - which is >tedious. Nothing has changed except for build process. > >Any comments? My view is that the rebuild will have to happen, since >the version number has to change. But I think it's an interesting >case.
If you make a change that in any substantial way affects the resulting .deb, you must increase the revision. That usually includes changed dependencies, changed build/install scripts, etc. But not changes made to the Desc* fields, or to the Source field, for example. The exact decision depends on the exact case. E.g. say you have a buildscript, and later it turns out that it will not work for people that have the GNU fileutils installed, and you make a change to it that ensures it works for these people, too, but which doesn't affect the genereated .deb, then you do *not* have to increment the revision. Reasoning: the people that succesfully built it will not get any difference. And the people that couldn't build it yet, well, they couldn't build it yet =) Max -- ----------------------------------------------- Max Horn Software Developer email: <mailto:[EMAIL PROTECTED]> phone: (+49) 6151-494890 _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
