- can you explain how I can get WEIDU_ARCH, WEIDU_OS and WEIDU_VER from --list-components-json
That's what you wanted? The change made for 247 is that the variables will evaluate to something if evaluated.
You can get the version from --version. I could maybe add some "built for WEIDU_OS and WEIDU_ARCH" line to the message.
No, I was confused by the way how it was written at the changelog. It was unusual so I asked. For the record, the --list-components-json is for components data only and let it stay that way.
- are you planning more changes to WeiDU package zip names and internal structure?
That was lazy and inconsiderate of me. And I suppose if I change it back to the way it used to be, I'll break things for you again.
So how do people prefer to download WeiDU? One package with all binaries for 32-/64-bit (old way) or one for each (inadvertent current way)? I'll have to re-do my packaging scripts either way.
Yep, I already updated bunch of code. I would say the way how it is now, separate packages by OS and architecture:
WeiDU-Windows-247-amd64.zip
WeiDU-Windows-247-x86.zip
WeiDU-Mac-247-amd64.zip
WeiDU-Linux-247-x86.zip
WeiDU-Linux-247-amd64.zip
It makes easy to get correct OS package directly, rather than search recursively against folder from extracted zip. You could also get rid of top-level directory inside zip.
Last thing: you can tag the new version but when you create release, have all packages ready and add them before publishing GitHib release. If you create release without packages, everything breaks.