Bug#357066: [Pbuilder-maint] Bug#357066: Support DEBUILD_LINTIAN* and DEBUILD_LINDA* variables?

Loïc Minier lool at dooz.org
Sun Sep 28 09:35:48 UTC 2008


 First, quick note: linda shouldn't be targetted anymore.

On Sat, Sep 27, 2008, Luca Capello wrote:
> +# lintian
> +if [ "${AUTO_LINTIAN}" = "yes" ]; then
> +    unset LINTIAN_PARAM || true
> +    if [ -n "${LINTIAN_OPTS}" ]; then
> +	LINTIAN_PARAM[1]="${LINTIAN_OPTS}"
> +    fi
> +    LINTIAN_PARAM[2]="${BUILDRESULT}/${PKG_SOURCENAME}_${PKG_VERSION}_${ARCHITECTURE}.changes"
> +    lintian "${LINTIAN_PARAM[@]}"
> +fi

 I personally am not happy with that approach promoted by default
 because it runs lintian on the host.  I agree it's easy and useful to
 do this, but I prefer the approach of running lintian in the build env.
   This is particularly useful when:
 - uploading for another release (preparing an upload for etch from sid,
   or for lenny from sid, or for sid from lenny)
 - uploading for another distro (preparing binaries for Ubuntu from
   Debian)

 I'm using a hook for this (attached).

 I'm happy if we implement both approaches, but I wouldn't like pbuilder
 to push people in relying on tools from the host to build packages
 which might be targetted at something else.

-- 
Loïc Minier
-------------- next part --------------
#!/bin/sh

set -e

install_packages() {
    apt-get -y --force-yes install "$@"
}

install_packages lintian

echo "+++ lintian output +++"

su -c "lintian -I --show-overrides /tmp/buildd/*.changes; :" - pbuilder

echo "+++ end of lintian output +++"



More information about the Pbuilder-maint mailing list