Menu
▾
▴
tcl-core — Tcl Core Team discussions about Tcl development
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(19) |
Jul
(96) |
Aug
(144) |
Sep
(222) |
Oct
(496) |
Nov
(171) |
Dec
(6) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(4) |
Feb
(4) |
Mar
(9) |
Apr
(4) |
May
(12) |
Jun
(6) |
Jul
|
Aug
|
Sep
(1) |
Oct
(2) |
Nov
|
Dec
|
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(52) |
Aug
(47) |
Sep
(47) |
Oct
(95) |
Nov
(56) |
Dec
(34) |
| 2003 |
Jan
(99) |
Feb
(116) |
Mar
(125) |
Apr
(99) |
May
(123) |
Jun
(69) |
Jul
(110) |
Aug
(130) |
Sep
(289) |
Oct
(211) |
Nov
(98) |
Dec
(140) |
| 2004 |
Jan
(85) |
Feb
(87) |
Mar
(342) |
Apr
(125) |
May
(101) |
Jun
(60) |
Jul
(151) |
Aug
(118) |
Sep
(162) |
Oct
(117) |
Nov
(125) |
Dec
(95) |
| 2005 |
Jan
(141) |
Feb
(54) |
Mar
(79) |
Apr
(83) |
May
(74) |
Jun
(125) |
Jul
(63) |
Aug
(89) |
Sep
(130) |
Oct
(89) |
Nov
(34) |
Dec
(39) |
| 2006 |
Jan
(98) |
Feb
(62) |
Mar
(56) |
Apr
(94) |
May
(169) |
Jun
(41) |
Jul
(34) |
Aug
(35) |
Sep
(132) |
Oct
(722) |
Nov
(381) |
Dec
(36) |
| 2007 |
Jan
(34) |
Feb
(174) |
Mar
(15) |
Apr
(35) |
May
(74) |
Jun
(15) |
Jul
(8) |
Aug
(18) |
Sep
(39) |
Oct
(125) |
Nov
(89) |
Dec
(129) |
| 2008 |
Jan
(176) |
Feb
(91) |
Mar
(69) |
Apr
(178) |
May
(310) |
Jun
(434) |
Jul
(171) |
Aug
(73) |
Sep
(187) |
Oct
(132) |
Nov
(259) |
Dec
(292) |
| 2009 |
Jan
(27) |
Feb
(54) |
Mar
(35) |
Apr
(54) |
May
(93) |
Jun
(10) |
Jul
(36) |
Aug
(36) |
Sep
(93) |
Oct
(52) |
Nov
(45) |
Dec
(74) |
| 2010 |
Jan
(20) |
Feb
(120) |
Mar
(165) |
Apr
(101) |
May
(56) |
Jun
(12) |
Jul
(73) |
Aug
(306) |
Sep
(154) |
Oct
(82) |
Nov
(63) |
Dec
(42) |
| 2011 |
Jan
(176) |
Feb
(86) |
Mar
(199) |
Apr
(86) |
May
(237) |
Jun
(50) |
Jul
(26) |
Aug
(56) |
Sep
(42) |
Oct
(62) |
Nov
(62) |
Dec
(52) |
| 2012 |
Jan
(35) |
Feb
(33) |
Mar
(128) |
Apr
(152) |
May
(133) |
Jun
(21) |
Jul
(74) |
Aug
(423) |
Sep
(165) |
Oct
(129) |
Nov
(387) |
Dec
(276) |
| 2013 |
Jan
(105) |
Feb
(30) |
Mar
(130) |
Apr
(42) |
May
(60) |
Jun
(79) |
Jul
(101) |
Aug
(46) |
Sep
(81) |
Oct
(14) |
Nov
(43) |
Dec
(4) |
| 2014 |
Jan
(25) |
Feb
(32) |
Mar
(30) |
Apr
(80) |
May
(42) |
Jun
(23) |
Jul
(68) |
Aug
(127) |
Sep
(112) |
Oct
(72) |
Nov
(29) |
Dec
(69) |
| 2015 |
Jan
(35) |
Feb
(49) |
Mar
(95) |
Apr
(10) |
May
(70) |
Jun
(64) |
Jul
(93) |
Aug
(85) |
Sep
(43) |
Oct
(38) |
Nov
(124) |
Dec
(29) |
| 2016 |
Jan
(253) |
Feb
(181) |
Mar
(132) |
Apr
(419) |
May
(68) |
Jun
(90) |
Jul
(52) |
Aug
(142) |
Sep
(131) |
Oct
(80) |
Nov
(84) |
Dec
(192) |
| 2017 |
Jan
(329) |
Feb
(842) |
Mar
(248) |
Apr
(85) |
May
(247) |
Jun
(186) |
Jul
(37) |
Aug
(73) |
Sep
(98) |
Oct
(108) |
Nov
(143) |
Dec
(143) |
| 2018 |
Jan
(155) |
Feb
(139) |
Mar
(72) |
Apr
(112) |
May
(82) |
Jun
(119) |
Jul
(24) |
Aug
(33) |
Sep
(179) |
Oct
(295) |
Nov
(111) |
Dec
(34) |
| 2019 |
Jan
(20) |
Feb
(29) |
Mar
(49) |
Apr
(89) |
May
(185) |
Jun
(131) |
Jul
(9) |
Aug
(59) |
Sep
(30) |
Oct
(44) |
Nov
(118) |
Dec
(53) |
| 2020 |
Jan
(70) |
Feb
(108) |
Mar
(50) |
Apr
(9) |
May
(70) |
Jun
(24) |
Jul
(103) |
Aug
(82) |
Sep
(132) |
Oct
(119) |
Nov
(174) |
Dec
(169) |
| 2021 |
Jan
(75) |
Feb
(51) |
Mar
(76) |
Apr
(73) |
May
(53) |
Jun
(120) |
Jul
(114) |
Aug
(73) |
Sep
(70) |
Oct
(18) |
Nov
(26) |
Dec
|
| 2022 |
Jan
(26) |
Feb
(63) |
Mar
(64) |
Apr
(64) |
May
(48) |
Jun
(74) |
Jul
(129) |
Aug
(106) |
Sep
(238) |
Oct
(169) |
Nov
(149) |
Dec
(111) |
| 2023 |
Jan
(110) |
Feb
(47) |
Mar
(82) |
Apr
(106) |
May
(168) |
Jun
(101) |
Jul
(155) |
Aug
(35) |
Sep
(51) |
Oct
(55) |
Nov
(134) |
Dec
(202) |
| 2024 |
Jan
(103) |
Feb
(129) |
Mar
(154) |
Apr
(89) |
May
(60) |
Jun
(162) |
Jul
(201) |
Aug
(61) |
Sep
(167) |
Oct
(111) |
Nov
(133) |
Dec
(141) |
| 2025 |
Jan
(122) |
Feb
(88) |
Mar
(106) |
Apr
(113) |
May
(203) |
Jun
(185) |
Jul
(124) |
Aug
(154) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Jan N. <jan...@gm...> - 2024-05-29 19:30:57
|
Op wo 29 mei 2024 om 18:20 schreef Andreas Kupries:
> With the Technote at that location mirroring synched it and now believes that
> it has nothing to synch anymore, despite more commits appearing __underneath__
> the TN.
So, the lesson is: no technotes in the future any more. Check!
Many thanks!
Jan Nijtmans
|
|
From: Andreas K. <and...@gm...> - 2024-05-29 16:20:18
|
> Oh boy. Ok, will have a look in the evening. > > commits", I have no idea but clearly there seems to be a problem somewhere > > in the mirroring. The "commit" the mirror looks to be stuck on, has the hash "fd076420b5b5". This is actually a technote, not a commit, and pre-dated into the future, July 10. It its an advert for the EuroTcl/OpenACS in that week. Because of the pre-dating it appears at the top of the timeline. The same top position is used by mirroring to determine the latest commit in fossil, to be compared to the last commit mirroring synched. With the Technote at that location mirroring synched it and now believes that it has nothing to synch anymore, despite more commits appearing __underneath__ the TN. This will fix itself on July 10. Which is a bit late. As a quick workaround I have now re-dated the TN to May 28, below the last commits made in the last few days, and started a manual mirror run. This should synch all the missing commits, and keep synching. More general however: !!! Please all note that fossil repositories have an "ad-unit" setting for exactly this use case. Setting this to a small HMTL block that block will be shown on __every__ page of the repository, just underneath the primary and secondary navbars. If this kind of thing is needed any admin of the repo can enter this. I will now enter an ad-unit refering to EuroTcl/OpenACS to all repos on core. After that I will delete/clean the TechNote. -- Happy Tcling, Andreas Kupries <and...@gm...> <https://core.tcl-lang.org/akupries/> <https://akupries.tclers.tk/> Developer @ SUSE Software Solutions Germany GmbH ------------------------------------------------------------------------------- |
|
From: Andreas K. <aku...@su...> - 2024-05-29 08:45:00
|
Oh boy. Ok, will have a look in the evening. On Wed, May 29, 2024 at 9:23 AM apnmbx-public--- via Tcl-Core < tcl...@li...> wrote: > I was referencing the Tcl repository. > https://core.tcl-lang.org/tcl/timeline > shows lots of commits since Friday. As to why the sync sees "no new > commits", I have no idea but clearly there seems to be a problem somewhere > in the mirroring. > > /Ashok > > -----Original Message----- > From: Andreas Kupries <and...@gm...> > Sent: Wednesday, May 29, 2024 12:12 PM > To: apn...@ya... > Cc: tcl...@li... > Subject: Re: [TCLCORE] github mirrors not syncing > > > > As of this morning the github mirror commits were several days old. > Perhaps > > something's broken in the mirroring? > > Any specific repositories you are concerned about ? > > Checking Tcl itself I see that the Friday sync transfered commits, and > since > then the sync sees "No new commits" in the fossil repository, i.e. has > nothing > to transfer. > > Fri May 24 23:38:04 PDT 2024 @ Sat May 25 00:15:12 PDT 2024 fx/peer | > Run > git --bare --git-dir /home/www/state/tcl/tmp remote add target > /home/www/state/tcl/git |& sed -e {s|\r|\n|g} | sed -e {s|^| |} | > Fri May 24 23:38:04 PDT 2024 @ Sat May 25 00:15:12 PDT 2024 fx/peer | > Run > git --bare --git-dir /home/www/state/tcl/tmp push --force target --all |& > sed > -e {s|\r|\n|g} | sed -e {s|^| |} | > Fri May 24 23:38:04 PDT 2024 @ To /home/www/state/tcl/git > Fri May 24 23:38:04 PDT 2024 @ 1804a74de..ff0d56551 > bug-18f4a94d03 > -> bug-18f4a94d03 > Fri May 24 23:38:04 PDT 2024 @ 3d24fb270..4eb4297f5 > core-8-6-branch -> core-8-6-branch > Fri May 24 23:38:04 PDT 2024 @ 8218333b6..4f540c600 > core-8-branch > -> core-8-branch > Fri May 24 23:38:04 PDT 2024 @ 874f40c34..bd90d9eb6 main -> > main > Fri May 24 23:38:04 PDT 2024 @ * [new branch] > bug-43b7e5b511 > -> bug-43b7e5b511 > Fri May 24 23:38:04 PDT 2024 @ * [new branch] > bug-e589d9bdab > -> bug-e589d9bdab > Fri May 24 23:38:04 PDT 2024 @ Sat May 25 00:15:13 PDT 2024 fx/peer | > Run > git --bare --git-dir /home/www/state/tcl/tmp push --force target --tags |& > sed > -e {s|\r|\n|g} | sed -e {s|^| |} | > Fri May 24 23:38:04 PDT 2024 @ Everything up-to-date > Fri May 24 23:38:04 PDT 2024 @ Imported new commits to git mirror in > 37 > min > Fri May 24 23:38:04 PDT 2024 @ Sat May 25 00:15:14 PDT 2024 fx/peer | > GitUpdateImported /home/www/state/tcl/git > fd076420b5b5c5d31d48c51a24e24a5881178 > 33d0d0b08dd0423e42fa1197737 | > Fri May 24 23:38:04 PDT 2024 @ OK > > -- > Happy Tcling, > Andreas Kupries <and...@gm...> > <https://core.tcl-lang.org/akupries/> > <https://akupries.tclers.tk/> > Developer @ SUSE Software Solutions Germany GmbH > > ---------------------------------------------------------------------------- > --- > > > > > > > > _______________________________________________ > Tcl-Core mailing list > Tcl...@li... > https://lists.sourceforge.net/lists/listinfo/tcl-core > -- Andreas Kupries - SUSE Software Solutions GmbH |
|
From: <apn...@ya...> - 2024-05-29 07:22:23
|
I was referencing the Tcl repository. https://core.tcl-lang.org/tcl/timeline shows lots of commits since Friday. As to why the sync sees "no new commits", I have no idea but clearly there seems to be a problem somewhere in the mirroring. /Ashok -----Original Message----- From: Andreas Kupries <and...@gm...> Sent: Wednesday, May 29, 2024 12:12 PM To: apn...@ya... Cc: tcl...@li... Subject: Re: [TCLCORE] github mirrors not syncing > As of this morning the github mirror commits were several days old. Perhaps > something's broken in the mirroring? Any specific repositories you are concerned about ? Checking Tcl itself I see that the Friday sync transfered commits, and since then the sync sees "No new commits" in the fossil repository, i.e. has nothing to transfer. Fri May 24 23:38:04 PDT 2024 @ Sat May 25 00:15:12 PDT 2024 fx/peer | Run git --bare --git-dir /home/www/state/tcl/tmp remote add target /home/www/state/tcl/git |& sed -e {s|\r|\n|g} | sed -e {s|^| |} | Fri May 24 23:38:04 PDT 2024 @ Sat May 25 00:15:12 PDT 2024 fx/peer | Run git --bare --git-dir /home/www/state/tcl/tmp push --force target --all |& sed -e {s|\r|\n|g} | sed -e {s|^| |} | Fri May 24 23:38:04 PDT 2024 @ To /home/www/state/tcl/git Fri May 24 23:38:04 PDT 2024 @ 1804a74de..ff0d56551 bug-18f4a94d03 -> bug-18f4a94d03 Fri May 24 23:38:04 PDT 2024 @ 3d24fb270..4eb4297f5 core-8-6-branch -> core-8-6-branch Fri May 24 23:38:04 PDT 2024 @ 8218333b6..4f540c600 core-8-branch -> core-8-branch Fri May 24 23:38:04 PDT 2024 @ 874f40c34..bd90d9eb6 main -> main Fri May 24 23:38:04 PDT 2024 @ * [new branch] bug-43b7e5b511 -> bug-43b7e5b511 Fri May 24 23:38:04 PDT 2024 @ * [new branch] bug-e589d9bdab -> bug-e589d9bdab Fri May 24 23:38:04 PDT 2024 @ Sat May 25 00:15:13 PDT 2024 fx/peer | Run git --bare --git-dir /home/www/state/tcl/tmp push --force target --tags |& sed -e {s|\r|\n|g} | sed -e {s|^| |} | Fri May 24 23:38:04 PDT 2024 @ Everything up-to-date Fri May 24 23:38:04 PDT 2024 @ Imported new commits to git mirror in 37 min Fri May 24 23:38:04 PDT 2024 @ Sat May 25 00:15:14 PDT 2024 fx/peer | GitUpdateImported /home/www/state/tcl/git fd076420b5b5c5d31d48c51a24e24a5881178 33d0d0b08dd0423e42fa1197737 | Fri May 24 23:38:04 PDT 2024 @ OK -- Happy Tcling, Andreas Kupries <and...@gm...> <https://core.tcl-lang.org/akupries/> <https://akupries.tclers.tk/> Developer @ SUSE Software Solutions Germany GmbH ---------------------------------------------------------------------------- --- |
|
From: Andreas K. <and...@gm...> - 2024-05-29 06:42:42
|
> As of this morning the github mirror commits were several days old. Perhaps
> something's broken in the mirroring?
Any specific repositories you are concerned about ?
Checking Tcl itself I see that the Friday sync transfered commits, and since
then the sync sees "No new commits" in the fossil repository, i.e. has nothing
to transfer.
Fri May 24 23:38:04 PDT 2024 @ Sat May 25 00:15:12 PDT 2024 fx/peer | Run
git --bare --git-dir /home/www/state/tcl/tmp remote add target
/home/www/state/tcl/git |& sed -e {s|\r|\n|g} | sed -e {s|^| |} |
Fri May 24 23:38:04 PDT 2024 @ Sat May 25 00:15:12 PDT 2024 fx/peer | Run
git --bare --git-dir /home/www/state/tcl/tmp push --force target --all |& sed
-e {s|\r|\n|g} | sed -e {s|^| |} |
Fri May 24 23:38:04 PDT 2024 @ To /home/www/state/tcl/git
Fri May 24 23:38:04 PDT 2024 @ 1804a74de..ff0d56551 bug-18f4a94d03
-> bug-18f4a94d03
Fri May 24 23:38:04 PDT 2024 @ 3d24fb270..4eb4297f5
core-8-6-branch -> core-8-6-branch
Fri May 24 23:38:04 PDT 2024 @ 8218333b6..4f540c600 core-8-branch
-> core-8-branch
Fri May 24 23:38:04 PDT 2024 @ 874f40c34..bd90d9eb6 main -> main
Fri May 24 23:38:04 PDT 2024 @ * [new branch] bug-43b7e5b511
-> bug-43b7e5b511
Fri May 24 23:38:04 PDT 2024 @ * [new branch] bug-e589d9bdab
-> bug-e589d9bdab
Fri May 24 23:38:04 PDT 2024 @ Sat May 25 00:15:13 PDT 2024 fx/peer | Run
git --bare --git-dir /home/www/state/tcl/tmp push --force target --tags |& sed
-e {s|\r|\n|g} | sed -e {s|^| |} |
Fri May 24 23:38:04 PDT 2024 @ Everything up-to-date
Fri May 24 23:38:04 PDT 2024 @ Imported new commits to git mirror in 37
min
Fri May 24 23:38:04 PDT 2024 @ Sat May 25 00:15:14 PDT 2024 fx/peer |
GitUpdateImported /home/www/state/tcl/git fd076420b5b5c5d31d48c51a24e24a5881178
33d0d0b08dd0423e42fa1197737 |
Fri May 24 23:38:04 PDT 2024 @ OK
--
Happy Tcling,
Andreas Kupries <and...@gm...>
<https://core.tcl-lang.org/akupries/>
<https://akupries.tclers.tk/>
Developer @ SUSE Software Solutions Germany GmbH
-------------------------------------------------------------------------------
|
|
From: <apn...@ya...> - 2024-05-29 04:58:14
|
As of this morning the github mirror commits were several days old. Perhaps something's broken in the mirroring? |
|
From: Marc C. <cul...@gm...> - 2024-05-29 01:26:11
|
According to this github page about their CI runners <https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners/about-github-hosted-runners> the macOS 11 image, which is the one used by the TclTk/Tk project on github, reaches end of life today, May 28. When the workflow file is updated to use macOS 14 there will be test failures. I have attempted to mitigate these in the macOS-14-CI branch. - Marc - Marc |
|
From: B H. <bra...@gm...> - 2024-05-24 01:19:13
|
> On May 23, 2024, at 17:47, Steve Landers <st...@di...> wrote: > > > The Tcl Core Team (TCT) is pleased to announce that Rolf Ade, Ashok Nadkarni and Harald Oehlmann have been elected to membership in the TCT, following the procedure described in TIP #0 https://core.tcl-lang.org/tips/doc/trunk/tip/0.md > > A warm welcome to all three! Congratulations! -bch > > Regards, > Steve, on behalf of the TCT > _______________________________________________ > Tcl-Core mailing list > Tcl...@li... > https://lists.sourceforge.net/lists/listinfo/tcl-core |
|
From: Steve L. <st...@di...> - 2024-05-24 00:46:36
|
The Tcl Core Team (TCT) is pleased to announce that Rolf Ade, Ashok Nadkarni and Harald Oehlmann have been elected to membership in the TCT, following the procedure described in TIP #0 https://core.tcl-lang.org/tips/doc/trunk/tip/0.md A warm welcome to all three! Regards, Steve, on behalf of the TCT |
|
From: Harald O. <har...@el...> - 2024-05-23 13:56:07
|
Dear TCL OO experts, ticket "Tcl_NewObjectInstance() silently ignores existing namespace argument" https://core.tcl-lang.org/tcl/tktview/154f0982f2f701a1c3f964c0a3d54737361a3630 now handles the error case with an API extension. Thanks Donal for the solution proposal. This can be seen as a design flaw as the error case was missed. Please put your opinion to the ticket until 31th of May 2024. Take care and thank you all, Harald |
|
From: Harald O. <har...@el...> - 2024-05-20 17:57:50
|
Appreciation to the whole team to make tihs happen ! Harald Am 20.05.2024 um 19:35 schrieb Donald G Porter via Tcl-Core: > Tcl/Tk 9.0b2 Release Announcement > May 20, 2024 > > The Tcl Core Team is pleased to announce the 9.0b2 releases of the Tcl > dynamic language and the Tk graphical interface package. These are the > second beta releases of Tcl 9.0 and Tk 9.0. More details can be found > below. > > We would like to express our gratitude to all those who submit bug > reports and patches. This information is invaluable in enabling us > to identify and eliminate problems in the core. Such reports can be > submitted here. > > https://core.tcl-lang.org/tcl/ticket > https://core.tcl-lang.org/tk/ticket > > We ask that you log in (anonymous if you wish) to create tickets. > This deters abuse of the ticketing system: > > https://core.tcl-lang.org/tcl/login > https://core.tcl-lang.org/tcl/login > > Where to get the new releases: > ------------------------------ > > Tcl/Tk 9.0b1 sources are freely available as open source from the Tcl > SourceForge project's file distribution area: > > https://sourceforge.net/projects/tcl/files/ > > This distribution is source code only. We keep links to some third > parties offering pre-built binaries for various systems here: > > https://www.tcl-lang.org/software/tcltk/bindist.html > > General Summary > --------------- > > These are new major versions of both Tcl and Tk. There are new features > to be enjoyed. There are incompatibilities to be considered. The list > of both is long and detailed and not fully included here. We believe many > scripts written for Tcl 8 will run unchanged in Tcl 9. We believe many > more > can be modified in small and simple ways to produce a new script that runs > in both Tcl 8 and Tcl 9. We expect that extensions and applications using > the public C APIs of Tcl and Tk will involve more effort, but that it is > still within reasonable reach to produce source code supporting both Tcl 8 > and Tcl 9 while both releases remain in widespread use. > > These are beta releases. The developers believe the new feature set is > complete enough and the code quality is high enough that it is time for > a larger audience of Tcl/Tk users to give them a try and report back > to the developers what difficulties need resolution before stable > releases of Tcl/Tk 9.0.0. > > The experiences of Tcl/Tk 8 users adapting their code to the beta releases > of Tcl/Tk 9 will shape the final interfaces of Tcl/Tk 9.0.0, and will > determine the need for possible Tcl/Tk 8.7 releases that might supply > additional lifecycle and migration support. > > It is not recommended to deploy these beta releases directly to mission > critical use without significant testing and review. > > Tcl Changes Summary > ------------------- > > The source code for Tcl is managed by fossil. Tcl developers coordinate > all > changes to the Tcl source code at > > > [Tcl Source Code](https://core.tcl-lang.org/tcl/timeline) > > Release Tcl 9.0b2 arises from the check-in with tag core-9-0-b2. > > Highlighted differences between Tcl 9.0 and Tcl 8.6 are summarized below, > with focus on changes important to programmers using the Tcl library and > writing Tcl scripts. > > ## 64-bit capacity: Data values larger than 2Gb > > ## Internationalization of text > - Full Unicode range of codepoints > - New encodings: utf-16/utf-32/ucs-2(le|be), CESU-8, etc. > - `encoding` options -profile, -failindex manage encoding of I/O. > - `msgcat` supports custom locale search list > - `source` defaults to -encoding utf-8 > > ## Zip filesystems and attached archives. > > ## Unix notifiers available using epoll() or kqueue() > - relieves limits on file descriptors imposed by legacy select() > > ## Notable incompatibilities > - Unqualified varnames resolved in current namespace, not global. > - No --disable-threads build option. Always thread-enabled. > - I/O malencoding default response: raise error (-profile strict) > - Windows platform needs Windows 7 or Windows Server 2008 R2 or later > - Ended interpretation of ~ as home directory in pathnames > - Removed the "identity" encoding > - $::tcl_precision no longer controls string generation of doubles > - Removed Tcl 7 legacies: [case], [puts] [read] variant syntaxes > - Removed subcommands [trace variable|vdelete|vinfo] > - No -eofchar option for channels anymore for writing. > - On Windows 10+ (Version 1903 or higher), system encoding is always > utf-8. > > ## Incompatibilities in C public interface > - Many arguments expanded type from int to Tcl_Size > - Ended support for Tcl_ChannelTypeVersion less than 5 > - Introduced versioning of the Tcl_ObjType struct > - Removed macros CONST*: Tcl 9 support means dropping Tcl 8.3 support > - Removed routines: > > Tcl_Backslash(), Tcl_*VA(), Tcl_*MathFunc*(), Tcl_MakeSafe(), > > Tcl_(Save|Restore|Discard|Free)Result(), Tcl_EvalTokens(), > > Tcl_(Get|Set)DefaultEncodingDir(), > > Tcl_UniCharN(case)cmp(), Tcl_UniCharCaseMatch() > > ## New commands > - `array default`, `array for` > - `coroinject`, `coroprobe` > - `clock add weekdays` > - `const`, `info const*` > - `dict getdefault` > - `file tempdir`, `file home`, `file tildeexpand` > - `info commandtype` > - `ledit` > - `lpop` > - `lremove` > - `lseq` > - `package files` > - `string insert`, `string is dict` > - `tcl::process` > - `*::build-info` > > ## New command options > - `regsub ... -command ...` > - `lsearch ... -stride ...` > - `clock scan ... -validate ...` > - `socket ... -nodelay ... -keepalive ...` > - `vwait` controlled by several new options > > ## Numbers > - 0NNN format is no longer octal interpretation. Use 0oNNN. > - 0dNNNN format to compel decimal interpretation. > - NN_NNN_NNN, underscores in numbers for optional readability > - Functions: isinf() isnan() isnormal() issubnormal() isunordered() > - `fpclassify` > - Function int() no longer truncates to word size > > ## tcl::oo facilities > - private variable and methods > - `method -export`, `method -unexport` > > Tk Changes Summary > ------------------- > > The source code for Tk is managed by fossil. Tk developers coordinate all > changes to the Tk source code at > > > [Tk Source Code](https://core.tcl-lang.org/tk/) > > Release Tk 9.0b2 arises from the check-in with tag core-9-0-b2. > > Highlighted differences between Tk 9.0 and Tk 8.6 are summarized below, > with focus on changes important to programmers using the Tk library and > writing Tcl scripts containing Tk commands. > > ## Many improvements to use of platform features and conventions. > - Built-in widgets and themes are scaling-aware. > - Improved support of two-finger gestures, where available > - The `tk windowingsystem` "aqua" needs macOS 10.10 or later > > ## New commands and options > - `tk sysnotify`: access to the OS notifications system > - `tk systray`: access to the OS tray facility > - `tk print`: access to the OS printing facility > > ## Widget options > - New `ttk::progressbar` option: **-text** > - `$frame ... -backgroundimage $img -tile $bool` > - `$menu id`, `$menu add|insert ... ?$id? ...` > - `$image get ... -withalpha ...` > - All indices now accept the forms **end**, **end-int**, **int+|-int** > > ## Improved widget appearance > - `ttk::notebook` with nondefault tab positions > > ## Images > - Partial SVG support > - Read/write access to photo image metadata > > Tcl Improvement Proposals (TIPs) > -------------------------------- > > Each new user-visible feature in Tcl or Tk should find its origins in > a Tcl Improvement Proposal (TIP). TIPs are published, edited, considered > and voted in public, and should contain valuable information about how > a feature came to be the way it is. See the full collection here: > > https://tip.tcl-lang.org/ > > Additional support resources > ---------------------------- > > See the following links for an accumulation of migration advice: > > https://core.tcl-lang.org/tcl/wiki?name=Migrating+C+extensions+to+Tcl+9 > https://core.tcl-lang.org/tcl/wiki?name=Migrating+scripts+to+Tcl+9 > > There has been much progress already porting many known applications, > extensions, and packages in the Tcl world to compatibility with Tcl/Tk 9: > > https://wiki.tcl-lang.org/page/Apps+confirmed+to+work+with+Tcl+9 > https://wiki.tcl-lang.org/page/Porting+extensions+to+Tcl+9 > > For additional information: > --------------------------- > > Please visit the Tcl Developer Xchange web site: > > https://www.tcl-lang.org/ > > This site contains a variety of information about Tcl/Tk in general, the > core Tcl and Tk distributions, Tcl development tools, and much more. > > -- > Tcl Core Team and Maintainers > Don Porter, Tcl Core Release Manager > |
|
From: Donald G P. <don...@ni...> - 2024-05-20 17:51:23
|
Tcl/Tk 9.0b2 Release Announcement May 20, 2024 The Tcl Core Team is pleased to announce the 9.0b2 releases of the Tcl dynamic language and the Tk graphical interface package. These are the second beta releases of Tcl 9.0 and Tk 9.0. More details can be found below. We would like to express our gratitude to all those who submit bug reports and patches. This information is invaluable in enabling us to identify and eliminate problems in the core. Such reports can be submitted here. https://core.tcl-lang.org/tcl/ticket https://core.tcl-lang.org/tk/ticket We ask that you log in (anonymous if you wish) to create tickets. This deters abuse of the ticketing system: https://core.tcl-lang.org/tcl/login https://core.tcl-lang.org/tcl/login Where to get the new releases: ------------------------------ Tcl/Tk 9.0b1 sources are freely available as open source from the Tcl SourceForge project's file distribution area: https://sourceforge.net/projects/tcl/files/ This distribution is source code only. We keep links to some third parties offering pre-built binaries for various systems here: https://www.tcl-lang.org/software/tcltk/bindist.html General Summary --------------- These are new major versions of both Tcl and Tk. There are new features to be enjoyed. There are incompatibilities to be considered. The list of both is long and detailed and not fully included here. We believe many scripts written for Tcl 8 will run unchanged in Tcl 9. We believe many more can be modified in small and simple ways to produce a new script that runs in both Tcl 8 and Tcl 9. We expect that extensions and applications using the public C APIs of Tcl and Tk will involve more effort, but that it is still within reasonable reach to produce source code supporting both Tcl 8 and Tcl 9 while both releases remain in widespread use. These are beta releases. The developers believe the new feature set is complete enough and the code quality is high enough that it is time for a larger audience of Tcl/Tk users to give them a try and report back to the developers what difficulties need resolution before stable releases of Tcl/Tk 9.0.0. The experiences of Tcl/Tk 8 users adapting their code to the beta releases of Tcl/Tk 9 will shape the final interfaces of Tcl/Tk 9.0.0, and will determine the need for possible Tcl/Tk 8.7 releases that might supply additional lifecycle and migration support. It is not recommended to deploy these beta releases directly to mission critical use without significant testing and review. Tcl Changes Summary ------------------- The source code for Tcl is managed by fossil. Tcl developers coordinate all changes to the Tcl source code at > [Tcl Source Code](https://core.tcl-lang.org/tcl/timeline) Release Tcl 9.0b2 arises from the check-in with tag core-9-0-b2. Highlighted differences between Tcl 9.0 and Tcl 8.6 are summarized below, with focus on changes important to programmers using the Tcl library and writing Tcl scripts. ## 64-bit capacity: Data values larger than 2Gb ## Internationalization of text - Full Unicode range of codepoints - New encodings: utf-16/utf-32/ucs-2(le|be), CESU-8, etc. - `encoding` options -profile, -failindex manage encoding of I/O. - `msgcat` supports custom locale search list - `source` defaults to -encoding utf-8 ## Zip filesystems and attached archives. ## Unix notifiers available using epoll() or kqueue() - relieves limits on file descriptors imposed by legacy select() ## Notable incompatibilities - Unqualified varnames resolved in current namespace, not global. - No --disable-threads build option. Always thread-enabled. - I/O malencoding default response: raise error (-profile strict) - Windows platform needs Windows 7 or Windows Server 2008 R2 or later - Ended interpretation of ~ as home directory in pathnames - Removed the "identity" encoding - $::tcl_precision no longer controls string generation of doubles - Removed Tcl 7 legacies: [case], [puts] [read] variant syntaxes - Removed subcommands [trace variable|vdelete|vinfo] - No -eofchar option for channels anymore for writing. - On Windows 10+ (Version 1903 or higher), system encoding is always utf-8. ## Incompatibilities in C public interface - Many arguments expanded type from int to Tcl_Size - Ended support for Tcl_ChannelTypeVersion less than 5 - Introduced versioning of the Tcl_ObjType struct - Removed macros CONST*: Tcl 9 support means dropping Tcl 8.3 support - Removed routines: > Tcl_Backslash(), Tcl_*VA(), Tcl_*MathFunc*(), Tcl_MakeSafe(), > Tcl_(Save|Restore|Discard|Free)Result(), Tcl_EvalTokens(), > Tcl_(Get|Set)DefaultEncodingDir(), > Tcl_UniCharN(case)cmp(), Tcl_UniCharCaseMatch() ## New commands - `array default`, `array for` - `coroinject`, `coroprobe` - `clock add weekdays` - `const`, `info const*` - `dict getdefault` - `file tempdir`, `file home`, `file tildeexpand` - `info commandtype` - `ledit` - `lpop` - `lremove` - `lseq` - `package files` - `string insert`, `string is dict` - `tcl::process` - `*::build-info` ## New command options - `regsub ... -command ...` - `lsearch ... -stride ...` - `clock scan ... -validate ...` - `socket ... -nodelay ... -keepalive ...` - `vwait` controlled by several new options ## Numbers - 0NNN format is no longer octal interpretation. Use 0oNNN. - 0dNNNN format to compel decimal interpretation. - NN_NNN_NNN, underscores in numbers for optional readability - Functions: isinf() isnan() isnormal() issubnormal() isunordered() - `fpclassify` - Function int() no longer truncates to word size ## tcl::oo facilities - private variable and methods - `method -export`, `method -unexport` Tk Changes Summary ------------------- The source code for Tk is managed by fossil. Tk developers coordinate all changes to the Tk source code at > [Tk Source Code](https://core.tcl-lang.org/tk/) Release Tk 9.0b2 arises from the check-in with tag core-9-0-b2. Highlighted differences between Tk 9.0 and Tk 8.6 are summarized below, with focus on changes important to programmers using the Tk library and writing Tcl scripts containing Tk commands. ## Many improvements to use of platform features and conventions. - Built-in widgets and themes are scaling-aware. - Improved support of two-finger gestures, where available - The `tk windowingsystem` "aqua" needs macOS 10.10 or later ## New commands and options - `tk sysnotify`: access to the OS notifications system - `tk systray`: access to the OS tray facility - `tk print`: access to the OS printing facility ## Widget options - New `ttk::progressbar` option: **-text** - `$frame ... -backgroundimage $img -tile $bool` - `$menu id`, `$menu add|insert ... ?$id? ...` - `$image get ... -withalpha ...` - All indices now accept the forms **end**, **end-int**, **int+|-int** ## Improved widget appearance - `ttk::notebook` with nondefault tab positions ## Images - Partial SVG support - Read/write access to photo image metadata Tcl Improvement Proposals (TIPs) -------------------------------- Each new user-visible feature in Tcl or Tk should find its origins in a Tcl Improvement Proposal (TIP). TIPs are published, edited, considered and voted in public, and should contain valuable information about how a feature came to be the way it is. See the full collection here: https://tip.tcl-lang.org/ Additional support resources ---------------------------- See the following links for an accumulation of migration advice: https://core.tcl-lang.org/tcl/wiki?name=Migrating+C+extensions+to+Tcl+9 https://core.tcl-lang.org/tcl/wiki?name=Migrating+scripts+to+Tcl+9 There has been much progress already porting many known applications, extensions, and packages in the Tcl world to compatibility with Tcl/Tk 9: https://wiki.tcl-lang.org/page/Apps+confirmed+to+work+with+Tcl+9 https://wiki.tcl-lang.org/page/Porting+extensions+to+Tcl+9 For additional information: --------------------------- Please visit the Tcl Developer Xchange web site: https://www.tcl-lang.org/ This site contains a variety of information about Tcl/Tk in general, the core Tcl and Tk distributions, Tcl development tools, and much more. -- Tcl Core Team and Maintainers Don Porter, Tcl Core Release Manager -- | Don Porter Applied and Computational Mathematics Division | | don...@ni... Information Technology Laboratory | | http://math.nist.gov/~DPorter/ NIST | |______________________________________________________________________| |
|
From: Francois V. <fvo...@fr...> - 2024-05-20 17:30:09
|
Here is the problem: https://core.tcl-lang.org/tk/tktview/ee397e0a55 Regards, Francois Le 20/05/2024 à 19:23, Harald Oehlmann a écrit : > Am 20.05.2024 um 16:45 schrieb apnmbx-public--- via Tcl-Core: >> Tested with VS 2022 on Win 10 x64 and x86. No Tcl failures (except I >> don't have tdbc drivers). 5 Tk failures, all having to do with >> clipboard busy error, which are nothing new. > > Ashok, > in my case, this is the vnc client, which keeps the clipboard busy for > monitoring. Eventually, Remote desktop has the same issue. There are > options about this in Remote desktop "Options->Local Resources->Apply > WIndows Key combinations" Which should be set to "Only in Full screen". > This option also has other side effects like loosing modifier keys on > the way... > > Just a guess, > Harald > > > > _______________________________________________ > Tcl-Core mailing list > Tcl...@li... > https://lists.sourceforge.net/lists/listinfo/tcl-core |
|
From: Harald O. <har...@el...> - 2024-05-20 17:23:48
|
Am 20.05.2024 um 16:45 schrieb apnmbx-public--- via Tcl-Core: > Tested with VS 2022 on Win 10 x64 and x86. No Tcl failures (except I don't have tdbc drivers). 5 Tk failures, all having to do with clipboard busy error, which are nothing new. Ashok, in my case, this is the vnc client, which keeps the clipboard busy for monitoring. Eventually, Remote desktop has the same issue. There are options about this in Remote desktop "Options->Local Resources->Apply WIndows Key combinations" Which should be set to "Only in Full screen". This option also has other side effects like loosing modifier keys on the way... Just a guess, Harald |
|
From: <apn...@ya...> - 2024-05-20 14:45:27
|
Tested with VS 2022 on Win 10 x64 and x86. No Tcl failures (except I don't have tdbc drivers). 5 Tk failures, all having to do with clipboard busy error, which are nothing new. Tested (Tcl only) with Ubuntu 20 (WSL). No test failures. Looks good to go afaict. /Ashok -----Original Message----- From: Donald G Porter via Tcl-Core <tcl...@li...> Sent: Friday, May 17, 2024 11:31 PM To: tcl...@li... Subject: Re: [TCLCORE] Tcl/Tk 9.0b2 Release Candidate Now available at https://sourceforge.net/projects/tcl/files/Tcl/9.0b2/ are RC3 candidate source code distribution pre-releases of Tcl 9.0b2 and Tk 9.0b2. This is the latest in a sequence of candidate releases leading to the release of Tcl/Tk 9.0b2. Testing of builds and operations on multiple platforms is invited. Open tickets on any problems discovered, or raise the issue in a reply to this message. The bundled packages included with Tcl 9.0b2 include sqlite 3.45.3 and release candidates of Itcl 4.2.5, tdbc* 1.1.8, and thread 3.0b2. These release candidates include fixes for bugs reported in the previous candidates or Tcl and Tk. The other packages include changes in the TEA build system. It is expected these files will become the Tcl/Tk 9.0b2 releases with a release date of May 20, 2024. Thank you for your contributions and assistance. -- | Don Porter Applied and Computational Mathematics Division | | don...@ni... Information Technology Laboratory | | http://math.nist.gov/~DPorter/ NIST | |______________________________________________________________________| _______________________________________________ Tcl-Core mailing list Tcl...@li... https://lists.sourceforge.net/lists/listinfo/tcl-core |
|
From: Harald O. <har...@el...> - 2024-05-18 08:31:09
|
Thanks, great work, I appreciate ! All clean on Win 64 platform, VS2015 32 bit nmake compiler ! Thanks, Harald Am 17.05.2024 um 20:01 schrieb Donald G Porter via Tcl-Core: > Now available at > > https://sourceforge.net/projects/tcl/files/Tcl/9.0b2/ > > are RC3 candidate source code distribution pre-releases of Tcl 9.0b2 and > Tk 9.0b2. > > This is the latest in a sequence of candidate releases leading to the > release of > Tcl/Tk 9.0b2. Testing of builds and operations on multiple platforms is > invited. > Open tickets on any problems discovered, or raise the issue in a reply > to this message. > > The bundled packages included with Tcl 9.0b2 include sqlite 3.45.3 and > release > candidates of Itcl 4.2.5, tdbc* 1.1.8, and thread 3.0b2. > > These release candidates include fixes for bugs reported in the previous > candidates > or Tcl and Tk. The other packages include changes in the TEA build system. > > It is expected these files will become the Tcl/Tk 9.0b2 releases with a > release date > of May 20, 2024. > > Thank you for your contributions and assistance. |
|
From: Donald G P. <don...@ni...> - 2024-05-17 18:35:22
|
Now available at https://sourceforge.net/projects/tcl/files/Tcl/9.0b2/ are RC3 candidate source code distribution pre-releases of Tcl 9.0b2 and Tk 9.0b2. This is the latest in a sequence of candidate releases leading to the release of Tcl/Tk 9.0b2. Testing of builds and operations on multiple platforms is invited. Open tickets on any problems discovered, or raise the issue in a reply to this message. The bundled packages included with Tcl 9.0b2 include sqlite 3.45.3 and release candidates of Itcl 4.2.5, tdbc* 1.1.8, and thread 3.0b2. These release candidates include fixes for bugs reported in the previous candidates or Tcl and Tk. The other packages include changes in the TEA build system. It is expected these files will become the Tcl/Tk 9.0b2 releases with a release date of May 20, 2024. Thank you for your contributions and assistance. -- | Don Porter Applied and Computational Mathematics Division | | don...@ni... Information Technology Laboratory | | http://math.nist.gov/~DPorter/ NIST | |______________________________________________________________________| |
|
From: Steve L. <st...@di...> - 2024-05-16 12:15:11
|
On 15 May 2024 at 10:44 PM +0800, Jan Nijtmans <jan...@gm...>, wrote: > Answering privately, (because I don't want too many people to know this .....) Your secret is safe with me - it’s the people I tell you can’t trust ;-) -- Steve |
|
From: Jan N. <jan...@gm...> - 2024-05-15 15:04:19
|
Op wo 15 mei 2024 om 16:52 schreef Donal Fellows:
> I’ll not merge either of these myself; I think it’s a good idea for others to review them. (The test suite works on my machine with both branches.)
I like both changes! The disadvantage is ..... everyone here is working
towards the 9.0b2 release, those kinds of changes should not cause
delay. So, please wait until after 9.0b2 before merging those.
Remember ....
https://core.tcl-lang.org/tcl/info/3a60363aa10ef993
This commit "Clean up a lot of small whitespace issues"
caused all builds going red:
https://github.com/tcltk/tcl/actions/runs/9075291504
And it created extra work for Don Porter, doing cherry-pick merges
to the b2-rc branch. I don't want to burden him with that.
Hope this helps,
Jan Nijtmans
|
|
From: Donal F. <don...@ma...> - 2024-05-15 15:02:14
|
That’s pretty simple to do. Make one of the workflow triggers be workflow-dispatch, with an parameter of which commit you’re talking about (defaulting to the current commit if you’ve got other triggers as well).
Here’s a cut-down (the parts not shown are entirely irrelevant to this discussion) fragment of a workflow I wrote for work which does this trick. You can trigger via the ReST API as well; you need a suitable API key for that, of course. (I mostly run the workflow this that I extracted this out of from within VSCode.)
on:
# Runs on pushes targeting the default branch
push:
branches: ['develop']
# Allows you to run this workflow manually from the Github Actions tab
workflow_dispatch:
inputs:
branch:
description: 'Name of branch to deploy.'
required: true
default: 'develop'
type: string
jobs:
deploy:
steps:
- name: Checkout
uses: actions/checkout@v4
with:
ref: ${{ github.event_name == 'workflow_dispatch' && inputs.branch || github.sha }}
It’s very convenient to be able to run a build (or deploy) for any commit whenever I need to. I hope this gives some hints about how to do it. (The official documentation says it all, but says so much more besides that it’s easier to have a pointer to how to do it…)
Donal.
From: Dipl. Ing. Sergey G. Brester via Tcl-Core <tcl...@li...>
However what we maybe need, is some button/API-call, triggering CI-run of certain GH-commit (without to modify .github\workflows\*.yml)... I must think about that a bit.
|
|
From: Donal F. <don...@ma...> - 2024-05-15 14:51:47
|
I've been trying out a couple of features of compilers that might be of interest going forward. They're broken out into their own branches. The first branch (called sentinel) enables the sentinel feature of GCC (the only compiler I've tested with; not enabled elsewhere) which allows the compiler to generate a warning if a terminating NULL is missing from a varargs call (useful for Tcl_AppendResult, not Tcl_PrintfObj). It works, and while it does change a public API, it does so to add a feature that everyone ought to have been following all along anyway; if your call to Tcl_AppendResult is missing that NULL, it was always broken and this just highlights it. I don't know if clang could pick this up too (probably!) but that can always be sorted out later. The second (called result-helpers) adds two internal macros, TclSetResult and TclPrintfResult. There are no changes to any public API. The TclSetResult macro is a simple wrapping of Tcl_SetObjResult and Tcl_NewStringObj (with a -1 length argument) that is just a super-common pattern in our code. The TclPrintfResult is very similar, except with Tcl_PrintfObj instead of Tcl_NewStringObj (another common pattern); it's mainly of interest because it is a C99 standard variadic macro, and I'm not sure how common the support for that is across our target compiler base (it works with the versions of GCC and MSVC I've got installed on this machine). These two trivial macros reduce the amount of visual clutter in our code, and are all just calls to the same underlying functions that were being used beforehand. I'll not merge either of these myself; I think it's a good idea for others to review them. (The test suite works on my machine with both branches.) Donal. |
|
From: Dipl. I. S. G. B. <se...@us...> - 2024-05-15 14:50:00
|
Well, not really privately (tcl-core was on CC)... I knew the trick (basically everyone who can read GHA-flow-yamls knows it) ;) The issue with core-prefix is (if forgotten to remove the tag) you don't know later why it was here. So my suggestion with ci-* is still valid. However the disadvantage with "next day" CI-run is still there. Regards, Serg. Am 15.05.2024 16:42, schrieb Jan Nijtmans: > Op wo 15 mei 2024 om 16:34 schreef Dipl. Ing. Sergey G. Brester via Tcl-Core: > ... > >> Alternatively one could surely add new on-push item (something like ci-*) for .githubworkflows*.yml, so if needed we could simply create a branch starting with ci-, so it'd trigger a CI-run on demand (without to modify yamls everytime). Although in opposite to above variant not immediately, but firstly after nightly run of fossil to git export (so less advantageous than other dev-repo with filtered). > > listinfo/tcl-core > > Answering privately, (because I don't want too many people to know this .....) > there is already such a possibility. Just add a tag "core-*" to the commit > you want to test, and the GITHUB build will be triggered overnight > (actually: in the morning). > > I added such a tag now, so tomorrow we will see the result. > > Regards, > Jan Nijtmans |
|
From: Jan N. <jan...@gm...> - 2024-05-15 14:43:06
|
Op wo 15 mei 2024 om 16:34 schreef Dipl. Ing. Sergey G. Brester via Tcl-Core:
...
> Alternatively one could surely add new on-push item (something like ci-*) for .github\workflows\*.yml, so if needed we could simply create a branch starting with ci-, so it'd trigger a CI-run on demand (without to modify yamls everytime). Although in opposite to above variant not immediately, but firstly after nightly run of fossil to git export (so less advantageous than other dev-repo with filtered).
listinfo/tcl-core
Answering privately, (because I don't want too many people to know this .....)
there is already such a possibility. Just add a tag "core-*" to the commit
you want to test, and the GITHUB build will be triggered overnight
(actually: in the morning).
I added such a tag now, so tomorrow we will see the result.
Regards,
Jan Nijtmans
|
|
From: Harald O. <har...@el...> - 2024-05-15 14:39:36
|
Great info and great ideas - Wizard style ! I appreciate your great work and tests on multiple platforms.. Nevertheless, I think to let the CI work for us is a good thing ;-). So, if you are able to initiate this, I would appreciate... With appreciation, Harald (the pedantic idiot) Am 15.05.2024 um 16:33 schrieb Dipl. Ing. Sergey G. Brester: > Ticket irrelevant info, so I'm sending via tcl-core... > > I don't think this fix necessarily needs a CI run, since the fix is > platform-independent (more or less, without to consider deeper > IO-bindings to native API) and I already tested it for windows/linux. > And it will be anyway tested later after merge to main branches. > > However what we maybe need, is some button/API-call, triggering CI-run > of certain GH-commit (without to modify .github\workflows\*.yml)... I > must think about that a bit. > For instance, I've own script fossil2git (very fast, because used > export-marks) where I can also filter/rewrite commits (so one could > rewrite on-push in yamls), then one could create new GH-repo for dev > purposes and export there from fossil, so that after push, the newest > commit could immediately trigger a single CI-run (no matter which branch). > > Alternatively one could surely add new on-push item (something like > ci-*) for .github\workflows\*.yml, so if needed we could simply create a > branch starting with ci-, so it'd trigger a CI-run on demand (without to > modify yamls everytime). Although in opposite to above variant not > immediately, but firstly after nightly run of fossil to git export (so > less advantageous than other dev-repo with filtered). > > Regards, > Serg. > >> Automated mail by fx, on behalf ofn...@tc... <mailto:no...@tc...> >> >> Ticket Change [c96fdb69104f12e878577be97927feaa2aee750d834bb91f05eeab114d6460e7] >> [refchan segfault] >> By oehhar >> For Tcl >> On 2024-05-15T13:26:16.934 >> Detailshttps://core.tcl-lang.org/tcl/tinfo?name=c96fdb69104f12e878577be97927feaa2aee750d834bb91f05eeab114d6460e7 <https://core.tcl-lang.org/tcl/tinfo?name=c96fdb69104f12e878577be97927feaa2aee750d834bb91f05eeab114d6460e7> >> Tickethttps://core.tcl-lang.org/tcl/tktview/79474c58800cdf94559a2c01230b4536aa416016 <https://core.tcl-lang.org/tcl/tktview/79474c58800cdf94559a2c01230b4536aa416016> >> >> Changed Fields >> icomment: Sebres, Jan, great work! maybe, it may be tested by the continuous >> integration. Jan may advise, how to do this. Jan modifies a certain >> file to test a certain branch and it is tested over night... >> >> Take care, Harald >> login: oehhar >> username: oehhar |
|
From: Dipl. I. S. G. B. <se...@us...> - 2024-05-15 14:33:43
|
Ticket irrelevant info, so I'm sending via tcl-core... I don't think this fix necessarily needs a CI run, since the fix is platform-independent (more or less, without to consider deeper IO-bindings to native API) and I already tested it for windows/linux. And it will be anyway tested later after merge to main branches. However what we maybe need, is some button/API-call, triggering CI-run of certain GH-commit (without to modify .githubworkflows*.yml)... I must think about that a bit. For instance, I've own script fossil2git (very fast, because used export-marks) where I can also filter/rewrite commits (so one could rewrite on-push in yamls), then one could create new GH-repo for dev purposes and export there from fossil, so that after push, the newest commit could immediately trigger a single CI-run (no matter which branch). Alternatively one could surely add new on-push item (something like ci-*) for .githubworkflows*.yml, so if needed we could simply create a branch starting with ci-, so it'd trigger a CI-run on demand (without to modify yamls everytime). Although in opposite to above variant not immediately, but firstly after nightly run of fossil to git export (so less advantageous than other dev-repo with filtered). Regards, Serg. > Automated mail by fx, on behalf of no...@tc... > > Ticket Change [c96fdb69104f12e878577be97927feaa2aee750d834bb91f05eeab114d6460e7] > [refchan segfault] > By oehhar > For Tcl > On 2024-05-15T13:26:16.934 > Details https://core.tcl-lang.org/tcl/tinfo?name=c96fdb69104f12e878577be97927feaa2aee750d834bb91f05eeab114d6460e7 [1] > Ticket https://core.tcl-lang.org/tcl/tktview/79474c58800cdf94559a2c01230b4536aa416016 [2] > > Changed Fields > icomment: Sebres, Jan, great work! maybe, it may be tested by the continuous > integration. Jan may advise, how to do this. Jan modifies a certain > file to test a certain branch and it is tested over night... > > Take care, Harald > login: oehhar > username: oehhar > > ------------------------------------------------------------ > See Tcl/Tk development @ http://core.tcl-lang.org/ [3] > ------------------------------------------------------------ Links: ------ [1] https://core.tcl-lang.org/tcl/tinfo?name=c96fdb69104f12e878577be97927feaa2aee750d834bb91f05eeab114d6460e7 [2] https://core.tcl-lang.org/tcl/tktview/79474c58800cdf94559a2c01230b4536aa416016 [3] http://core.tcl-lang.org/ |
26 messages has been excluded from this view by a project administrator.
