A question about precompiled packages

[K4sum1]

You mention "For now I won't publish a precompiled package (the install scripts are insanely slow on Windows)" on the 1.84.0-beta blog post, but this doesn't make much sense to me. As someone who has built Rust on Windows, I've found python x.py install doesn't work on Windows due to the sh command being missing. Instead I've used python x.py dist to package the compiler for use on another computer, and from what I remember, that process should be pretty quick. Although it creates multiple .tar.xz files and I combine those into one .7z for my releases.

This method of releasing does work, at least for my uses with eRust. Maybe something with the config.toml idk. Here's the config.toml I use to build if you want to look.

Edit: I just realized I didn't use a question mark so maybe the wording in the title isn't entirely correct, maybe concern would fit better idk.

[seritools]

I've found python x.py install doesn't work on Windows due to the sh command being missing

It certainly worked on my system, iirc it used the git-bash environment to run the shell scripts.

Although it creates multiple .tar.xz files and I combine those into one .7z for my releases.

do you have an automatic script that does this? I avoided using dist exactly because those files with multiple nested folders etc.

[K4sum1]

do you have an automatic script that does this? I avoided using dist exactly because those files with multiple nested folders etc.

I don't, I wouldn't know how to do this, nor do I compile Rust often enough, even if I were to follow major version releases to feel like I need to bother. I still manually repackage r3dfox into it's portable .7z form from the .zip files MozillaBuild outputs, and I release that relatively often.