I strongly recommend downloading the latest version of QB64PE only from the standard place which is:
https://staging.qb64phoenix.com/forumdisplay.php?fid=47
Only from there! In the past wacky things were done to help confuse others especially the ones hopping Linux distros. For example there is an AUR package for the "dot-rip" version from late last year, the last release never updated! It's not going to have the few commands added or being added to QB64PE.
Packages for a given Linux distro work OK for Freebasic, for example because it works well for the Freebasic team at one end, and for the users at the other end caring about it. It could be difficult to build and/or to hunt down the dependencies if the ordinary "tarball" were taken. No problem for Windows, just unpack to a directory not protected by M$ and start right away, just like QB64PE.
Somebody might have the crazy idea of packaging QB64PE into a DEB or RPM or something like that. Then it becomes his/her responsibility to update that package, because nobody else is going to volunteer for it! I might be wrong, but a "standard distro package" is just not a good idea. QB64PE was meant to work on any Linux distro but it's more complicated than it seems. All distros are supposed to have "gcc" installed but it doesn't mean the C++ compiler is included, which is a shame. The user has to be prepared for rare events like I've went through with Solus (don't use this particular distro anymore).
https://staging.qb64phoenix.com/forumdisplay.php?fid=47
Only from there! In the past wacky things were done to help confuse others especially the ones hopping Linux distros. For example there is an AUR package for the "dot-rip" version from late last year, the last release never updated! It's not going to have the few commands added or being added to QB64PE.
Packages for a given Linux distro work OK for Freebasic, for example because it works well for the Freebasic team at one end, and for the users at the other end caring about it. It could be difficult to build and/or to hunt down the dependencies if the ordinary "tarball" were taken. No problem for Windows, just unpack to a directory not protected by M$ and start right away, just like QB64PE.
Somebody might have the crazy idea of packaging QB64PE into a DEB or RPM or something like that. Then it becomes his/her responsibility to update that package, because nobody else is going to volunteer for it! I might be wrong, but a "standard distro package" is just not a good idea. QB64PE was meant to work on any Linux distro but it's more complicated than it seems. All distros are supposed to have "gcc" installed but it doesn't mean the C++ compiler is included, which is a shame. The user has to be prepared for rare events like I've went through with Solus (don't use this particular distro anymore).