|
From: Marc C. <cul...@gm...> - 2019-10-09 19:55:10
|
We are now getting 0 failures in the test suite when the catalina_more_tests branch is used on a macOS Catalina system (i.e. on my computer). We should run the tests on other macOS versions before merging. More importantly, we need to test the catalina_more_tests branch on other platforms for the following reason. When I looked at textDisp.test I was shocked at the overuse of the update command, especially given that our own wiki <https://wiki.tcl-lang.org/page/update> strongly advises against using it. I mean, really, what are you testing when you need to use commands like update ; update ; update and how exactly is that different from update ; update ; update ; update ? In textDisp.test I replaced hundreds of calls to update with calls to update idletasks without causing any new failures on the mac. In the end, there were only about 5 places where it seemed that update was needed. However, maybe "update ; update ; update" really is needed on some platform. Who knows? Also, Jan replaced some calls to update with calls to vwait and thereby eliminated some test failures. But, again, who knows about other platforms? There are several other test scripts that overuse update, but I used up all of my patience fixing textDisp.test and so I left many unnecessary calls to update in place. - Marc On Wed, Oct 9, 2019 at 1:22 PM Brad Lanam <bra...@gm...> wrote: > And another good variable for bash to get rid of the message > about bash deprecation and zsh shell default: > export BASH_SILENCE_DEPRECATION_WARNING=1 > put in your .bash_profile > > Before, in PackageInfo, I had > install-location="/tmp" > > and I moved or copied the package into its final install location > ($HOME/Desktop/BallroomDJ.app). > Yes, that's not so normal, but it works for me. > Did not work so well with the new installer. > > I don't have code-signing (can't afford that), not to mention, I don't use > XCode to generate the package. > So with Catalina I *must* install in the user home directory. > > PackageInfo: > install-location="/tmp" > enable_localSystem="false" > enable_anywhere="true" > enable_currentUserHome="true" > > This ignores install-location and installs to the desktop automatically. > I don't know if all of those new enable_* are needed, but it seems to work. > > On Wed, Oct 9, 2019 at 11:06 AM Marc Culler <cul...@gm...> wrote: > >> It is specifically mentioned when you run /usr/bin/wish >> >> $ /usr/bin/wish >> DEPRECATION WARNING: The system version of Tk is deprecated and may be >> removed in a future release. Please don't rely on it. Set >> TK_SILENCE_DEPRECATION=1 to suppress this warning. >> >> What changes did you have to make to your package?? >> >> - Marc >> >> On Wed, Oct 9, 2019 at 12:57 PM Brad Lanam <bra...@gm...> >> wrote: >> >>> Mac OS Catalina has a new security model. >>> Anyone producing .pkg or .dmg files needs to check and make >>> sure their installation process works. >>> >>> Fortunately, with a little research and much flailing around, my .pkg is >>> working again. >>> >>> Python2, ruby, perl will be removed from the next release of Mac OS. >>> Tcl (8.5.9) is not specifically mentioned, but I would not surprised if >>> it >>> got removed also. >>> >>> >>> On Wed, Oct 9, 2019 at 7:20 AM Donal K. Fellows < >>> don...@ma...> wrote: >>> >>>> On 09/10/2019 04:43, Marc Culler wrote: >>>> > I am not in favor of accepting test failures. >>>> >>>> Nobody is, but if we can't fix (or define a way to reliably skip when >>>> the test is known to fail for silly reasons unrelated to what is really >>>> being tested) then what other alternative is there? >>>> >>>> Donal. >>>> _______________________________________________ >>>> Tcl-Core mailing list >>>> Tcl...@li... >>>> https://lists.sourceforge.net/lists/listinfo/tcl-core >>>> >>> _______________________________________________ >>> Tcl-Core mailing list >>> Tcl...@li... >>> https://lists.sourceforge.net/lists/listinfo/tcl-core >>> >> |