Re: Recent changes in dpkg
On 05/24/2010 11:05 AM, Raphael Hertzog wrote:
> The versions 1.15.6 and 1.15.7 of dpkg introduced several important changes.
> Let's skim over them:
> * dpkg-dev provides a new script called dpkg-buildflags that packages
> should use in debian/rules to retrieve the default value of various
> compilation flags. Bug #578597 has been submitted against
> debian-policy. When generalized this offer us centralized archive-wide
> control of the default build flags as well as the possibility for
> end-users to try out easily new flags.
So you plan to enforce something which resulted in a lot of FTBFS due to the
fact that buildflags, which were written into a Makefile by configure or similar
tools, were overridden by the default values from dpkg again as they were still
present in the environment?
> * The plan concerning dpkg-source and the default source format has been
> clarified. In the long term, the default format will disappear and
> debian/source/format will become mandatory. The lintian tag
> missing-debian-source-format will help us track that.
Which will force developers to touch most of the packages in the archive just to
realize this? Sorry, but that's insane. You should not try to force people into
migrating to some new format because *you* think it is better. This is not a
decision which should be decided by the dpkg maintainers - instead it needs to
be discussed within the developers and maintainers. While the new format
provides some advantages when it comes to the handling of patches, the 1.0
format is still much more flexible to use - for example it does not require an
existing tarball to build a package, which is very useful for testing.
You know that there are a lot of arguments against the 3.0 format out there, so
please do not enforce such changes without discussing them first.
Bernd Zeimetz Debian GNU/Linux Developer
GPG Fingerprints: 06C8 C9A2 EAAD E37E 5B2C BE93 067A AD04 C93B FF79
ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F