- Add libuv submodule (only needed and built on Windows)
- Temporarily switch uWebSockets to my github repo: I submitted some
mingw compilation fixes upstream; as soon as a new upstream release
comes out we will switch this back to the upstream repo.
- Switch BOOST_SCOPE_EXIT to LOKI_DEFER
- Don't compile `closefrom()` on Windows (it isn't used, and generates
an unused function warning).
GCC version was already far older than we actually support, and various
other things were out of date as well.
Notable update:
- Replace libboost-all-dev with individual boost packages; the former
installs of a ton of crap that you don't need at all.
- Eliminate most of the Raspberry Pi section. The only useful thing in
it is a message about needing swap, everything else is just useless
noise.
- Add a link to the deb repo in the "Packages" section.
This makes three big changes to how translation files are generated:
- use Qt5 cmake built-in commands to do the translations rather than
calling lrelease directly. lrelease is often not in the path, while Qt5
cmake knows how to find and invoke it.
- Slam the resulting files into a C++ file using a cmake script rather
than needing to compile a .c file to generate C++ file. This is
simpler, but more importantly avoids the mess needed when cross
compiling of having to import a cmake script from an external native
build.
- In the actual generated files, use an unordered_map rather than a
massive list of static variable pointers.
- libzmq required version was much older than we actually require
- libnorm and libpgm are transitive dependencies of libzmq3, it makes no
sense to list them here (rather the libzmq3-dev package should depend on
them if they are needed).
- gtest is now always build from the submodule copy
- the readline dev package was wrong for debian/ubuntu.
There's really no reason to submodule it - we work with pretty much any
libunbound version, and it's a very commonly available library
(comparable to sqlite3 or boost, which we don't submodule).
This removes the submodule and switches it to a hard dependency.
From the FreeBSD architecture handbook (https://www.freebsd.org/doc/en/books/arch-handbook/jail-restrictions.html) as it relates to `allow.sysvipc`, "By default, this sysctl is set to 0. If it were set to 1, it would defeat the whole purpose of having a jail; privileged users from the jail would be able to affect processes outside the jailed environment." This is undesirable behavior.
Per `man jail`, regarding `allow.sysvipc`, "A process within the jail has access to System V primitives. This is deprecated in favor of the per-module parameters."
Since FreeBSD 11, the new way to deal with this (the per-module parameters) is with: `sysvshm`, for shared memory, `sysvsem`, for semaphores, and `sysvmsg`, for message queues. These can be set selectively to either `disable`; `inherit`, for the previous behavior (problematic due to UID collision, apparently); and `new`, for new behavior that avoids the UID collision problem.
Monero only uses semaphores, therefore we should recommend that jails be run with `sysvsem="new"` in the jail's jail.conf. Tested on FreeBSD 12.1.
Also, Monero is now able to be downloaded as a package or built from ports as `monero-cli` with a versioned suffix. It's got `Monero 'Carbon Chamaeleon' (v0.15.0.1-release)` as of right now, and it's been there 2-3 months, meaning it's currently and timely.
10 block lock time is for incoming outputs and not only incoming transactions (outgoing transaction has an incoming change output that is also locked for 10 blocks)
Kee Jefferys
Sean
Joshalosh
Sean Darcy
Jason Rhinelander
javabudd
Doyle
luigi1111
Alexander Blair
scoobybejesus
selsta
rating89us
TheCharlatan
moneromooo-monero
Gingeropolous
TheGoose
Riccardo Spagni
Kevin Crumb
erciccione
Guillaume Le Vaillant