![]() ![]() ![]() ![]() A feature that isn’t supposed to affect Tcl 8.6 is actually affecting Tcl 8.6, and as a result, the web site is hiding the Exe and MSI format installers. “Maybe things aren’t working the way you expect on your webpage.” There are more than two different build systems counting the ones that are not yet in production use, but users do not have access to any of the controls that instruct The Platform on which of the systems to build with. The Platform is a Build System As A Service. There isn’t a zip file installer for ActiveTcl, and has never been a zipfile installer not even all the way back to Tcl 8.3. In order to work with a bootstrap installer like this one, the build needs to be created on the build system that matches, and ActiveTcl 8.6 is not from that build system. You’re downloading a zipfile bootstrap installer, which only contains The State Tool and a set of instructions (which don’t work with Tcl 8.6) for downloading the rest of the components it needs from The Platform. That’s because you’re not downloading the installer for Tcl. “Do you realise that the ZIP file that is downloaded for Windows is only 2k?” Please fix the zip file issue so I can get working with the software I require, then get the EXE’s and msi’s up and running again. No there isn’t, there isn’t even one build system! You don’t offer exe or msi format installers for Tcl, so we have to use the state tool. If we offer a downloadable exe or msi format installer Maybe things aren’t working the way you expect on your webpage. There is a ‘Download Builds’ tab with no ability to download either EXE or MSIĪfter forking the project, there is no option to rebuild the project under my dashboard to try and generate a valid zip file This will be a guide as to how well you read and consider this feedback.ĭo you realise that the ZIP file that is downloaded for Windows is only 2k? (So clearly invalid) I’ll do the following in point form to make it easier to address and respond to each issue in turn. I’ve tried again to get this working, but no. Unpacking completed with FAILURE: Could not unpack artifact C:\Users\cs69\AppData\Local\activestate\cache\ff89621e_runtime_temp\1cd4b539-63da-5d8d-87e2-38b941008db1.zipįirst off, really disappointed in your response above. To increase the verbosity of these log files use the ACTIVESTATE_CLI_BUILD_VERBOSE=true environment variable The file then decompresses and promptly gets replaced when you try to activate again. Using 7Zip for extraction gets the following message: Double clicking on the file makes Windows come up and say the file is faulty. Found that the unzipping of the bundle in C:\Users\cs69\AppData\Local\ActiveState\cache\ff89621e_runtime_temp doesn’t work. ![]() Hi All, Also first time user but dug a bit deeper. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |