[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: config.* in the diff?

Hi Ross!

You wrote:

> clean:
> 	dh_testdir
> 	dh_testroot
> 	rm -f build-stamp 
> 	-$(MAKE) distclean
> 	-test -r /usr/share/misc/config.sub && \
> 	  cp -f /usr/share/misc/config.sub config.sub
> 	-test -r /usr/share/misc/config.guess && \
> 	  cp -f /usr/share/misc/config.guess config.guess
> 	dh_clean

This doesn't really make much sense. In my packages, I copy the new
config.{sub,guess} over the old ones in one of the build targets,
and put a backup of the original ones back in the clean target. That
way, the packages always use an up-to-date config.{sub,guess}, but the
diff isn't clobbered in any way because of this.

> For the moment I commented these the cp lines out, and restored the
> original files from the tarball. However, what is the "proper" solution
> to this?

The best solution is of course to get upstream include up-to-date
config.{sub,guess}. But just letting the clean target do what it's
supposed to do (i.e. clean the source tree).

Kind regards,
| Bas Zoetekouw                  | Si l'on sait exactement ce   |
|--------------------------------| que l'on va faire, a quoi    |
| zoetekw@phys.uu.nl             | bon le faire?                |
|    bas@A-Es2.uu.nl             |               Pablo Picasso  |

Reply to: