Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: James Knight <james.d.knight@live.com>,
	Fabrice Fontaine <fontaine.fabrice@gmail.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libglib2: bump version to 2.76.4
Date: Mon, 7 Aug 2023 23:54:41 +0200	[thread overview]
Message-ID: <20230807235441.69eaa921@windsurf> (raw)
In-Reply-To: <20230726171923.334017-1-bernd@kuhls.net>

Hello Bernd,

On Wed, 26 Jul 2023 19:19:23 +0200
Bernd Kuhls <bernd@kuhls.net> wrote:

> From: James Knight <james.d.knight@live.com>
> 
> - Drop `iconv` option since it was obsolete and dropped [1][2].

This fix has nothing to do with the version bump. The issue already
exists in 2.76.1 that we have today in Buildroot, so mixing this fix
with a version bump does not make sense.

So I've applied a commit that only fixes the libiconv issue:

  https://gitlab.com/buildroot.org/buildroot/-/commit/ff050de534eed1dab152890d748952fc659882a0

(I hope I didn't screw it up)

No, we will need a new commit on top of that to bump to 2.76.4. When
doing changes in the bump, always wonder if they are related to the
bump or not. If they are not, they should be a separate commit.

> - Ensure `nls` is explicitly configured based on `BR2_SYSTEM_ENABLE_NLS`
>    being set.
> - Cleanup configuration and dependency options (ordering, having a
>    common variable to share between host/target builds, adding more
>    explicit assignment of options).

For example this has nothing to do with the bump, so it should be a
separate commit. Except that neither Yann nor myself find the sharing
of config options in a "common" variable to be relevant, so we'd prefer
not to have this change.

Once again, really important: a bump should do a bump, and *only*
things related to the bump. If something is not related to the bump =>
separate commit.

Thanks!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2023-08-07 21:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-26 17:19 [Buildroot] [PATCH 1/1] package/libglib2: bump version to 2.76.4 Bernd Kuhls
2023-07-28 20:15 ` Thomas Petazzoni via buildroot
     [not found] ` <20230728221509.1127286e__5257.07515641756$1690575343$gmane$org@windsurf>
2023-07-30 10:54   ` Bernd Kuhls
2023-07-30 11:27     ` Thomas Petazzoni via buildroot
2023-07-30 12:09       ` Bernd Kuhls
2023-07-30 12:09         ` Bernd Kuhls
2023-08-07 21:54 ` Thomas Petazzoni via buildroot [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=20230807235441.69eaa921@windsurf \
    --to=buildroot@buildroot.org \
    --cc=bernd@kuhls.net \
    --cc=fontaine.fabrice@gmail.com \
    --cc=james.d.knight@live.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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