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

Re: Environment variables, debian/rules and dpkg-buildpackage

Goswin von Brederlow wrote:
Holger Levsen <holger@layer-acht.org> writes:


On Sonntag, 10. Mai 2009, Raphael Hertzog wrote:
With the include approach, we lack this feature and bad/broken local
overrides can't be detected if we only have the build log at hand.
which reminds me that we dont have build logs for probably a lot more than 25% (*) of the most used packages in the archive. The ones build manually by the developer...

I would really like to see that binaries for all archs are (re-)build on builds and that those logs are kept archived and linked from the PTS. (And arch all too of course).


(*) wild guess, asuming that most packages are upload on amd64/i386/powerpc and mostly used on i386.

Debuild already creates a build log. I think it would be nice to
include that file in the changes file and have DAK forward it to
buildd.debian.org for archival. git-buildpackage, svn-buildpackage,
... or even dpkg-buildpackage could do this too.

but I would like to have more :-)
Currently I prefer to build package with --quiet flag, so that I see
easily problems on building package:
I see that a lot of my sponsoree forgot to check *carefully* logs,
to look for deprecated features, or important but non fatal warnings.

So I would like to have a short log (e.g. what I put in stdout/stderr,
with "./configure --quiet"), so that people will have no excuses for
not be carefukll, but also to have access to configure.log (or/and
other build time log), on build failure.

Is it to much to ask?

Reply to: