On Tue, 11 Feb 2025 12:31:13 +0100 Stefan Hagen <sh+openbsd-po...@codevoid.de> wrote:
> izzy Meyer wrote (2025-02-10 23:34 CET): > [...] (snip) > > Hmm... > > ===> Checking files for luanti-5.10.0 > >> Fetch https://github.com/minetest/minetest/archive/refs/tags/5.10.0.tar.gz > >> Size does not match for minetest-minetest-5.10.0.tar.gz > > $ make makesum: > -SHA256 (minetest-minetest-5.10.0.tar.gz) = > KjFhwE5ziWCABvASgO2jBQf4us+h1rZMKvG4IKYtJnc= -SIZE > (minetest-minetest-5.10.0.tar.gz) = 12257502 +SHA256 > (minetest-minetest-5.10.0.tar.gz) = > E8VZVmk3z9ntHN5ZTCDnq1L4be4IFroS6CixS7jixqw= +SIZE > (minetest-minetest-5.10.0.tar.gz) = 12257396 > > $ make > ===> Extracting for luanti-5.10.0 > ===> Patching for luanti-5.10.0 > ===> Applying OpenBSD patch patch-src_CMakeLists_txt > patch: **** can't cd to > /usr/ports/pobj/luanti-5.10.0/minetest-5.10.0: No such file or > directory > > Looks like upstream changed the folder inside the tarball and > uploaded it again with the same version :( > > There's also a new repository now (luanti-org/luanti), and the old > repository is forwarding to the new one. > > I changed DIST_TUPLE to point to the new repository (same tarball > checksum). This aligns DISTNAME and PKGNAME as it should be. Thanks, I didn't catch that. > Further changes: (I'm working on this on jasperla's openbsd-wip repository, so I'll upload these changes to that repo) > - updated the license information. The included fonts are APLv2 > - @comment bin/minetest{,server} those are symlinks to > luanti{,server}. It's debatable if we want to keep those, but if not, > we can avoid the minetest/luanti conflict. Well, the old games/minetest is an old engine release of what is now called luanti. IMHO the correct way to do this is to completely remove the minetest port, and put a luanti port in its place. Though this doesn't ensure a direct upgrade path. Any ideas? > - added post-install target to rename net.minetest.minetest.desktop > and net.minetest.minetest.metainfo.xml to net.luanti.luanti... That's cos the migration hasn't fully finished in the backend yet. I'd rather not touch what upstream does until they do it on their end for maintainability's sake. > - Changed the test target to run luanti --run-unittests instead of > minetest --run-unittests Good catch, again. "luanti" is the correct binary to test, though it is symlinked to "minetest" which is why I didn't catch this. > With these changes, there's no conflict between minetest and luanti > from a port perspective. So both could be installed at the same time. I'm unsure on the solution here, but I suppose is seems fairly reasonable for now. Maybe a pkg-message for minetest is a way we can tell users to migrate to luanti? (snip) > > When testing luanti, I had mixed results. I could play online, but a > few times, the UI didn't render (all black) and I could only see my > arm move. I haven't seen this issue, probably cos I don't use the devtest game. > I saw that the games/minetest port downloads the minetest_game > repository. There's no 5.10 tag and no luanti_game repository. minetest_game *was* an old base game for minetest, but it is no longer bundled with the engine. minetest/luanti is an engine that the user can build on top of with installable "games" or "mods" to build what they like. The little plus button on the bottom left of the main menu lets you browse what they call the "ContentDB", and download the game you like. A popular one is VoxeLibre for example. Mesecraft is another biggie. > But there's a difference in the game, when I click "Start Game", > I can switch to the minetest game at the bottom. In luanti, I'm stuck > stuck in this "Development Test" screen. > > Left minetest, right luanti: https://ptrace.org/minetest-luanti.png > > When starting a game from the Development Test screen, it shows a > permanent text at the top of the screen that this is only meant for > development and testing. > > Do you know what's going on there? Is the actual game missing? :} Yes. Luanti is *just* a game engine like I said above. As such, there is no game bundled with luanti OOTB. Devtest is needed for the tests to pass, hence why it is bundled in the installed package. If you want a full game, grab one from the ContentDB. I found things work fine that way. > Maybe we should wait one or two point releases until the rebranding > is complete? Maybe? I guess having a pkg-message for games/minetest like I said, to inform users of minetest that they should migrate to games/luanti would be the best shot. Thoughts? -- iz (she/her) > i like to say mundane things, > there are too many uninteresting things > that go unnoticed. izder456 (dot) neocities (dot) org
