patches « android « build - minetest.git - modified minetest for gpcfs purposes

Mode	Name	Size
-rw-r--r--	irrlicht-back_button.patch	779	log plain
-rw-r--r--	irrlicht-native_activity.patch	368	log plain
-rw-r--r--	irrlicht-texturehack.patch	7948	log ### Advtrains Privilege Guide All privileges are automatically granted to singleplayer, but for multiplayer servers this might be interesting. In this document, "protected from" means the player does NOT have access to the area, while "protected by" means the player has (semi-)exclusive access to the area. There are 3 groups of privileges introduced by advtrains: ## Trains For a player to build his own trains and driving them, the player needs the 'train_operator' privilege. This privilege no longer allows him to control any train, only the ones that he owns or that he is whitelisted on. The owner of a wagon can write a whitelist which players are allowed to operate his wagon using the wagon properties dialog. Players having the 'train_admin' privilege can always drive, build and destroy any train. ## Tracks* The area 1 node around and 4 nodes up from each track node is protected. Players that don't have the 'track_builder' privilege can not build or dig (or modify) anything inside this area. If a player has this privilege and tries to modify anything that is in the area of a track node which is protected from him, he also can not do this. (that said, while checking protection, the area around a track is treated as the track node itself) Note that having 'protection_bypass' automatically implies 'track_builder' due to internal engine mechanics. (see comments in source code) ## Tua6f784835244111c90c05b6aae47092c2c5763a7'>libiconv_stdio.patch	629	log plain
-rw-r--r--	libvorbis-libogg-fpu.patch	1335	log plain
-rw-r--r--	openssl_arch.patch	2057	log plain