-
Notifications
You must be signed in to change notification settings - Fork 230
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v1.21.0 Busybox returns the same version of v.1.20? #97
Comments
Both releases correspond to upstream BusyBox 1.37, so that's not expected to change. The |
Quite by chance I've just released FRP-5236. There isn't much of any importance there. |
Thanks, Ron! 709f676 |
With FRP-5236 the w64devkit build of busybox-w32 now has a manifest which allows
This was discussed in busybox-w32 issue 366. In the README there's a link to the upsteam BusyBox man page. I have a man page on my website which is closer to the w64devkit version: BusyBox.html. |
From the next release the busybox-w32
Had this feature been available in earlier releases the versions reported by w64devkit would have been:
and
|
Thanks for the heads up, Ron! |
The default EXTRAVERSION is .git. Use some clues to determine a more precise EXTRAVERSION: - git describe - A .frp_describe file embedded in the release tarball - The name of the build directory: tarballs of release tags from GitLab and GitHub include the version in the directory name.
I just checked with v1.21.0:
and with the previous v1.20:
Looks like that version number is the same, with only a change in the compilation date - and the following character encoding information, as well.
Is this right?
[EDIT] Oh well, and the Busybox calling stubs are now marked as trojan by AVG, but this is another matter... 🙄
The text was updated successfully, but these errors were encountered: