Re: Misc development news (#6)
On Tue, 15 Apr 2008, Alexander Wirt wrote:
> Aren't the dpkg maintainers able to get such things fixed in advance of
> uploading dpkg? I'm still missing an announcement (of course before the
> upload) about that "feature".
> I don't think that such an important package as dpkg should be handled
> like this.
> Again I don't think that a package like dpkg should be handled like this.
If you want to teach us how to maintain dpkg, please join
email@example.com and subscribe to the git commit notices (PTS
with cvs keyword). It's very low traffic and you'll be able to
comment while things are developed.
Note: mistakes do happen and nobody is perfect. So next time you want to
give some _advice_, make it sound like an advice and not like a complaint.
> > Since dpkg 1.14.17, dpkg-buildpackage will define the environment
> > variables CFLAGS, CXXFLAGS, CPPFLAGS, LDFLAGS and FFLAGS. The goal is to
> > be able to easily recompile packages with supplementary compilation flags
> > and to simplify the debian/rules files since CFLAGS has the right default
> > value (no need to special case for DEB_BUILD_OPTIONS=noopt).
> At first I thought: WTF? Why are such important changes to the build
> enviroment not announced and discussed before they are introduced?
Would you like to check the bug log before saying such stuff?
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465282 points to
and I fail to see your comments in that thread.
> Additionally it's really really bad timing.
Which is why, while preparing the upload, we discussed it with the release
Le best-seller français mis à jour pour Debian Etch :