radareorg/radare2-release

Releasing is hard

radare2-release

This repository contains the scripts needed to create a new release of radare2.

Dependencies

• OSX (required to build iOS and OSX packages), but Linux works too
• Docker. Required to build the debian packages for amd64 and i686
• NDK (for the android builds), eventually dockerified
• make and sh
• rsync to publish the bins

Usage

• Edit CONFIG and update the version if needed
• Run make
• Check out/${VERSION}

What it builds right now:

[*] radare2-1.0.2 tarball is ok
[*] Already got radare2-extras-1.0.tar.gz
[*] Already got radare2-bindings-1.0.tar.gz
[*] Already got radare2-r2pipe-1.0.tar.gz
[*] radare2-1.0.2-android-x86 is already done
[*] radare2-1.0.2-android-mips is already done
[*] radare2-1.0.2-android-arm is already done
[*] radare2-1.0.2-android-aarch64 is already done
[*] Mingw32 package already done...
[*] Linux amd64 package already done...
[*] Linux i686 package already done...
[*] macOS package already done...
[*] iOS arm package already done...
[*] iOS arm64 package already done...
[*] iOS appstore package already done...
[*] found radare2-w32-1.0.2.zip
[*] found radare2_1.0.2_amd64.deb
[*] found radare2_1.0.2_i686.deb
[*] found radare2-1.0.2.pkg
[*] found radare2-arm32_1.0.2_iphoneos-arm.deb
[*] found radare2_1.0.2_iphoneos-arm.deb
[*] found radare2-ios-arm64-1.0.2.tar.gz
[*] Computing checksums...
[*] Publishing Cydia packages...
[*] Building the android app...
[*] Publishing Android binaries...
[*] Already published 1.0.2 android build for radare2-x86
[*] Already published 1.0.2 android build for radare2-arm
[*] Already published 1.0.2 android build for radare2-mips
[*] Already published 1.0.2 android build for radare2-aarch64
[*] Updating IRC channel title...
[*] Updating the website...

Future (aka TODO)

• Also release acr, valabind, ired and sdb
• Sign releases

radare2-release's Issues

Add nacl target

https://hub.docker.com/r/rlincoln/nacl-sdk/~/dockerfile/

Build the webuis

Use dockcross for emscripten target

output() returns No such file or directory for every target

$ make
[*] radare2-1.2.0-git tarball is ok
[*] Already got radare2-extras-1.1.0.tar.gz
[*] Already got radare2-bindings-1.0.1.tar.gz
[*] Already got radare2-r2pipe-1.1.0.tar.gz
[*] Already got radare2-webui-1.0.tar.gz
[*] Preparing radare2-1.2.0-git in tmp/android-x86...
[*] Building android-x86...
cp: cannot stat 'radare2-1.2.0-git-android-x86.tar.gz': No such file or directory
[*] Preparing radare2-1.2.0-git in tmp/android-mips...
[*] Building android-mips...
cp: cannot stat 'radare2-1.2.0-git-android-mips.tar.gz': No such file or directory
[*] Preparing radare2-1.2.0-git in tmp/android-arm...
[*] Building android-arm...
cp: cannot stat 'radare2-1.2.0-git-android-arm.tar.gz': No such file or directory
[*] Preparing radare2-1.2.0-git in tmp/android-aarch64...
[*] Building android-aarch64...
cp: cannot stat 'radare2-1.2.0-git-android-aarch64.tar.gz': No such file or directory
[*] Preparing radare2-1.2.0-git in tmp/debian-i686...

tmp/ vs /work

symlink tmp/radare2-* to work/ ?

Make release scripts a GitHub Action in radare2 repository

So they will be ran automatically to generate the release bins.

Radare2-release don't release windows installer anymore

This is regression. Release for windows on mikelloc used to be windows installer which are generated currently by appveyor:

• https://ci.appveyor.com/api/buildjobs/48682fq42njra3h6/artifacts/radare2_installer-vs2017_64.exe

• https://ci.appveyor.com/api/buildjobs/2iixnw09rw43fy76/artifacts/radare2_installer-vs2017_64_dyn.exe

You can check the appveyor script to see how to use innosetup: https://github.com/radare/radare2/blob/master/.appveyor.yml

Make hardened builds too

Build tiny static binaries for every arch

linux-x86
linux-arm
android-arm64
...

Add ASAN targets

Add target to build/update the Termux package

Add target to build the RPM

Add VS2019 builds

See for example the https://ci.appveyor.com/project/radare/radare2/builds/27896907/job/salgyx451tgpedhs/artifacts

emscripten compilation warnings

clang-3.9: warning: argument unused during compilation: '-pie'
WARNING:root:emcc: cannot find library "util"
warning: emitted code will contain very large numbers of local variables, which is bad for performance (build to JS with -O2 or above to avoid this - make sure to do so both on source files, and during 'linking')

... just a warning, says @trufae

Add post-release checks

Verify that all download links from the website work

Ensure that out/ contains all the expected build files

etc

Publishing requires interaction

To avoid disasters i think that before publishing we should do something like:

echo "Press enter to publish the new release or ^C to abort"
read A

Push bins to the radare2's release github page

Include -extras -r2pipe .. in release-notes/

Do some download stats page or tool

• curl https://api.github.com/repos/radare/radare2/releases|jq .| grep -e '"name"' -e download_count |less
• https://pypistats.org/packages/r2pipe
• https://radare.mikelloc.com/stats.html

Add static build for mips

Useful for routers

Build SDK zips like Frida does

Use gh-release

https://github.com/progrium/gh-release