These fortunes make a lot of people unconfortable and can be trigering
for some. Even if they are not active by default, they should have no
place here if you are trying to be a welcoming project.
There are a lot of other ways to be quirky and fun, I see no logical
reason to have these fortunes knowing they will negatively impact
people.
Signed-off-by: Filipe Laíns <lains@riseup.net>
* Use meson install instead of manual installation in meson.py
* Update AppVeyor and docs to use the new meson.py flag format
* Meson.py should use --prefix for install paths and --install is a boolean for Windows and Unix now.
* Removed windows specific restrictions from meson.py
* Ensure that the prefix path is an absolute path
* Fix install options syntax
* Added an optional rootdir path for the meson setup command
Co-authored-by: yossizap <yossizap@users.noreply.github.com>
* Introduce the "devmode" confinement
* Switch base to "core18"
* Install ninja and acr as build dependencies
* Add documentation on how to install from Snap
Co-authored-by: Simos Xenitellis <simos.lists@googlemail.com>
Provide a proper package ID to get rid of the following error:
`No receipt for 'radare2.pkg' found at '/'.`
Prepend a `/` for each returned path by the `pkgutil` command, to make
it an absolute path instead of a relative one.
Avoid invoking the `sudo` command for each file, which speeds up the
command significantly.
Avoid ambiguous signing certificates on macOS.
If a user manually installed a new code signing certificate into the
login keychain as documented, the install script will fail to sign r2
because the `sys/macos-cert.sh` script generates a new certificate in
the System keychain. This results in the following error when signing:
```
org.radare.radare2: ambiguous (matches "org.radare.radare2" in /Users/user/Library/Keychains/login.keychain-db and "org.radare.radare2" in /Library/Keychains/System.keychain)
```
To be constistent with `sys/macos-cert.sh`, change manual certificate
generation steps to install to System keychain instead of login
keychain.
Mention that code signing certificate generation is automated by the
install script before listing the manual steps to generate a new
code signing certificate.
* The image is generated with Gimp, saving as .data (RGB)
* This is 128(W) * 3(RGB) * ?(H) .. the height is computed with the blocksize
* r2 -e hex.cols=128 -qqfcpri doc/cows128.data
