From: Andreas K. <and...@gm...> - 2022-04-27 07:13:49
|
> On Tue, Apr 26, 2022 at 5:39 PM Andreas Kupries <and...@gm...> > wrote: > > > I actually still test Tcllib release RCs against 8.5. > > 8.4 even. > > > > Specifically > > 8.4.20 > > 8.5.19 > > 8.6.10 > > 8.7.a4 (*) > > > > > > (*) Just to look ahead for possible issues. > > Failures there are not blockers and not acted on. > OK, good to know! In any case, the fact remains that code (such as > struct::disjointsets) that loaded in Tcl 8.5 on earlier Tcllib > releases now may have declared Tcl 8.6 dependencies. That's sort of > a silent regression, since I'm sure your test process simply ignores > packages with a declared dependency on a newer release. .. Checking ... Ok, disjointset declares a 8.6 dependency in the code (package require), the tests (testsNeedTcl), and the package index (if vsatisfies guard). The latter means that it cannot be loaded into 8.5 anymore because it would not be registered at all. However, having thought about it, having a package X declare an 8.6 dependency in the tests while still having an 8.5 dependency declaration in code and package index, yes, that kind of mismatch and regression I would indeed miss. Even the `./sak.tcl validate versions` only compares package and index version information, and ignores version information in the tests. -- Happy Tcling, Andreas Kupries <and...@gm...> <https://core.tcl-lang.org/akupries/> <https://akupries.tclers.tk/> Developer @ SUSE Software Solutions Germany GmbH ------------------------------------------------------------------------------- |