All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Sam James <sam@gentoo.org>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: Please consider reducing build system churn
Date: Sun, 28 Apr 2024 10:37:23 +0200	[thread overview]
Message-ID: <Zi4KyftBnQZtr82G@debian> (raw)
In-Reply-To: <87ttjm8ero.fsf@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 2748 bytes --]

Hey Sam!

On Sun, Apr 28, 2024 at 02:19:55AM +0100, Sam James wrote:
> Hi,
> 
> I had a request to bump man-pages in Gentoo [0] and I must admit that
> I've been fatigued recently, both by other work, but also the large
> number of build system changes between man-pages releases.
> 
> I already try to review all build system changes but Recent Events (TM)
> means that one must take even more care and not be fatigued by changes.

Yup, I had the same feeling.  :-)

> man-pages in particular is a critical package and if I can't review its
> changes properly, I can't package updates to it.
> 
> There's a lot of churn commits like
> * d0d2e2f9a21e623db208b599643e7728d71e7e6f,

The rationale for that is that I diffed the whole build system of this
project with liba2i's, to reduce maintainance work.  Any spurious
difference was removed if it was unnecessary.

> * 57d0f8b4f1ba43fd4c4bfbe826d1b255c6ef9fd5,
> * cdb8bd9563dd8a0d32138de40bc64f0c3475790c,

This one was because man2html(1) crashed on a page from tzdb (which we
import).  I guess that's a necessary change.

> * 6658bc41a8d66afbf348126f8adcffe86227e2e1,
> * d7b3f23c53d83ff714dd829c929a27f2c05aab23,
> * 7de1139b82571dfe55224022e05e095a32b1ea89

This one was requested by Debian, so that known lint failures don't
pollute their packaging checks.

> and many others.

Those that I didn't comment, or the many others, were triggered by your
feedback that the build system was complex and hard to understand.  I've
been trying to keep it very organized.  But yeah, all that was prior to
Recent Events (TM), and I want to reduce build system churn
significantly from now on.

> 
> With regard to d0d2e2f9a21e623db208b599643e7728d71e7e6f specifically, it
> might be worth explaining: a) what liba2i is; b) what commits were
> actually pulled in (possibly with 'cherry-picked from ...' or shortlog
> output or something at least.)

I didn't cherry-pick anything specifically; I run diffoscope(1) between
both trees, and tried to remove the trivial differences such as white
space, so that it only shows the important diff.

> Alex already knows my feelings on homebrew complex Makefiles so I won't
> repeat them here, but I will say that homebrew complex Makefiles
> combined with a high amount of regular refactoring makes life much
> harder.
> 
> Please consider either getting all the refactoring out of the way if
> possible or reducing the amount of churn in the build system.

Agree.

Have a lovely Sunday!
Alex

> [0] https://bugs.gentoo.org/930798
> 
> thanks,
> sam



-- 
<https://www.alejandro-colomar.es/>
A client is hiring kernel driver, mm, and/or crypto developers;
contact me if interested.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-04-28  8:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-28  1:19 Please consider reducing build system churn Sam James
2024-04-28  8:37 ` Alejandro Colomar [this message]
2024-04-28 18:36   ` Alejandro Colomar

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=Zi4KyftBnQZtr82G@debian \
    --to=alx@kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=sam@gentoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.