linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Bastian Germann <bage@debian.org>
Cc: linux-xfs@vger.kernel.org, Emanuele Rocca <ema@debian.org>
Subject: Re: [PATCH] debian: Increase build verbosity, add terse support
Date: Mon, 12 Feb 2024 15:29:14 -0800	[thread overview]
Message-ID: <20240212232914.GT616564@frogsfrogsfrogs> (raw)
In-Reply-To: <20240212230813.10122-1-bage@debian.org>

On Tue, Feb 13, 2024 at 12:07:55AM +0100, Bastian Germann wrote:
> Section 4.9 of the Debian Policy reads:
> 
> "The package build should be as verbose as reasonably possible,
> except where the terse tag is included in DEB_BUILD_OPTIONS".
> 
> Implement such behavior for xfsprogs by passing V=1 to make by default.
> 
> Link: https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules
> Link: https://bugs.debian.org/1063774
> Reported-by: Emanuele Rocca <ema@debian.org>
> Signed-off-by: Bastian Germann <bage@debian.org>

Sounds good to me!
Reviewed-by: Darrick J. Wong <djwong@kernel.org>

--D

> ---
>  debian/rules | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/debian/rules b/debian/rules
> index 57baad62..7e4b83e2 100755
> --- a/debian/rules
> +++ b/debian/rules
> @@ -7,6 +7,10 @@ ifneq (,$(filter parallel=%,$(DEB_BUILD_OPTIONS)))
>      PMAKEFLAGS += -j$(NUMJOBS)
>  endif
>  
> +ifeq (,$(filter terse,$(DEB_BUILD_OPTIONS)))
> +    PMAKEFLAGS += V=1
> +endif
> +
>  package = xfsprogs
>  develop = xfslibs-dev
>  bootpkg = xfsprogs-udeb
> -- 
> 2.43.0
> 
> 

      reply	other threads:[~2024-02-12 23:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Zco4xFPmGJQshw7n@ariel>
2024-02-12 23:07 ` [PATCH] debian: Increase build verbosity, add terse support Bastian Germann
2024-02-12 23:29   ` Darrick J. Wong [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240212232914.GT616564@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=bage@debian.org \
    --cc=ema@debian.org \
    --cc=linux-xfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).