Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New package: vkdoom-0.9 #46506

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

SpidFightFR
Copy link
Contributor

@SpidFightFR SpidFightFR commented Oct 7, 2023

Testing the changes

  • I tested the changes in this PR: YES

New package

Local build testing

  • I built this PR locally for my native architecture, (x64-GlibC)

Hey fellas !
I'll be making this PR for something new on my side: adding a package to void.

The package is VKDoom, it's a ZDoom port, focused around Vulkan and modern technologies.
Compared to GZDoom (already in the repos), we could potentially see a visual upgrade, in vkdoom.

EDIT: After a talk with members of the project, vkdoom won't bring direct improvements (like prboom-plus-rt would do for example), but it brings a nice set of new features for mapmakers to allow way more detailed maps than GZDoom allowed to do so far. - Idk for you guys, but knowing this, vkdoom now feels even more interesting for the future of Doom !

It's not released yet, so this PR will be a draft for now. But i'll make sure to post a new template, tested, when it's released.

Peace ! ✌️

@SpidFightFR
Copy link
Contributor Author

Ah and for the record, here the builds fail, IT IS NORMAL !

It is because the v0.9 (version i'm using for this draft) was just a proof of concept, i actually built a "git" version of the package a while ago, on void, for my voidlinux pc, and it works. The V1 will correct this issue. 😄

@classabbyamp classabbyamp added the new-package This PR adds a new package label Oct 8, 2023
@SpidFightFR
Copy link
Contributor Author

ah yikes ! i tried to add the desc of the VKDoom project but it seems too long, imma shorten that a bit 😅

@SpidFightFR SpidFightFR force-pushed the vkdoom-void branch 3 times, most recently from f1a35f2 to 0c5b448 Compare October 10, 2023 06:58
@SpidFightFR
Copy link
Contributor Author

one last commit to fix the patch i also did for gzdoom (but adapted here for vkdoom), see #46503 (comment) for more info.

Copy link

github-actions bot commented Jan 9, 2024

Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it.

@github-actions github-actions bot added the Stale label Jan 9, 2024
@SpidFightFR
Copy link
Contributor Author

Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it.

We're still waiting on V1, bot 🥲

@SpidFightFR
Copy link
Contributor Author

SpidFightFR commented Feb 11, 2024

Finally some new stuff here !

So we got nightly build, i updated my PR so that people can try vkdoom. But the full V1 release isn't here yet so we have to wait before publishing this PR. 😅

@SpidFightFR
Copy link
Contributor Author

SpidFightFR commented Feb 11, 2024

Side note: the version_dev flag is purely temporary and is meant to be gone at V1, when this PR will be finished. (his is why the lint check fails, no worries this will be gone.)

Copy link

Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it.

@github-actions github-actions bot added the Stale label May 12, 2024
@SpidFightFR
Copy link
Contributor Author

Still waiting for V1.

@github-actions github-actions bot removed the Stale label May 13, 2024
@SpidFightFR SpidFightFR changed the title New package: vkdoom-0.9. New package: vkdoom-0.9 May 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new-package This PR adds a new package
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants