All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: linux-man <linux-man@vger.kernel.org>
Subject: Please consider reducing build system churn
Date: Sun, 28 Apr 2024 02:19:55 +0100	[thread overview]
Message-ID: <87ttjm8ero.fsf@gentoo.org> (raw)

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

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.

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,
* 57d0f8b4f1ba43fd4c4bfbe826d1b255c6ef9fd5,
* cdb8bd9563dd8a0d32138de40bc64f0c3475790c,
* 6658bc41a8d66afbf348126f8adcffe86227e2e1,
* d7b3f23c53d83ff714dd829c929a27f2c05aab23,
* 7de1139b82571dfe55224022e05e095a32b1ea89
and many others.

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.)

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.

[0] https://bugs.gentoo.org/930798

thanks,
sam

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

             reply	other threads:[~2024-04-28  1:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-28  1:19 Sam James [this message]
2024-04-28  8:37 ` Please consider reducing build system churn Alejandro Colomar
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=87ttjm8ero.fsf@gentoo.org \
    --to=sam@gentoo.org \
    --cc=linux-man@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 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.