Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Shubham Chakraborty <chakrabortyshubham66@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/tcl: bump to version 9.0.3
Date: Sun, 31 May 2026 08:11:30 +0200	[thread overview]
Message-ID: <ahvQtE5hSLGHtjej@windsurf> (raw)
In-Reply-To: <20260503081204.963653-1-chakrabortyshubham66@gmail.com>

On Sun, May 03, 2026 at 01:42:03PM +0530, Shubham Chakraborty wrote:
> Major version upgrade from 8.6 to 9.0 series.
> 
> Key changes in Tcl 9.0:
> - Full Unicode support (UTF-16/UTF-32/UCS-2 encodings)
> - 64-bit integer support
> - Enhanced encoding with -profile/-failindex options
> - Script library packaged with binary
> - Improved virtual filesystem support

Where is this list of key changes coming from? It doesn't match with
what is at https://www.tcl-lang.org/software/tcltk/9.0.html. Is this
just AI-generated slop?

> Also remove bundled itcl and thread packages to reduce bloat.

And this will not break existing users? Is it because those packages
are new?

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

  reply	other threads:[~2026-05-31  6:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-03  8:12 [Buildroot] [PATCH] package/tcl: bump to version 9.0.3 Shubham Chakraborty
2026-05-31  6:11 ` Thomas Petazzoni via buildroot [this message]
2026-08-10 11:31 ` [Buildroot] [PATCH v2] " Shubham Chakraborty
2026-08-24 20:24   ` Thomas Petazzoni via buildroot

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=ahvQtE5hSLGHtjej@windsurf \
    --to=buildroot@buildroot.org \
    --cc=chakrabortyshubham66@gmail.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