[ISSUE] Suggestion - Drop PrBoom+ (prboom-plus) Now That's Unmaintained And Most Of Its Forks Are Already Packaged

[ISSUE] Suggestion - Drop PrBoom+ (prboom-plus) Now That's Unmaintained And Most Of Its Forks Are Already Packaged

[TeusLollo]

[-- Attachment #1: Type: text/plain, Size: 3269 bytes --]

New issue by TeusLollo on void-packages repository

https://github.com/void-linux/void-packages/issues/45051

Description:
When `dsda-doom` was packaged at pull https://github.com/void-linux/void-packages/pull/32880, it was suggested by https://github.com/void-linux/void-packages/pull/32880#issuecomment-931756835 to drop `prboom-plus` entirely, although eventually the idea was renounced https://github.com/void-linux/void-packages/pull/32880#issuecomment-1086905621

Well, it appears now that `prboom-plus` is unmainted at https://github.com/coelckers/prboom-plus, and, indeed, the following links confirm that as a matter of fact:

https://doomwiki.org/wiki/PrBoom%2B 
The wiki explicitly lists `prboom-plus` as "discontinued"

https://www.doomworld.com/forum/topic/106866-prboom-2666-jun-20-2023/?page=57 
Fabian, main `prboom-plus` project director, quote for quote, stated the following:

_Hey people,
I'd like to announce that I just tagged the PrBoom+ 2.6.66 release!
https://github.com/coelckers/prboom-plus/releases/tag/v2.6.66
This is just a maintenance release to make the changes that have accumulated over the past 1.5 years available to all users who cannot build the sources themselves. Please do not mistake this as a sign of active development!
Future development will continue to take place in DSDA-Doom [1]. Or, for those who like to stay closer to the original code base, check out JadingTsunami's PrBoomX [2].
[1] https://github.com/kraflab/dsda-doom
[2] https://github.com/JadingTsunami/prboomX_ 

So, it appears they did one last update to v. 2.6.66, but _"do not mistake this as a sign of active development!"_.
`prboom-plus` seems to have been abandoned, thus. 

Now, for its successors, `dsda-doom` is already packaged, while `prboomX` looks like a one-dev project that already shows no signs of active development, thus I personally don't think it's worth it to package it, at least for now. 

At https://github.com/void-linux/void-packages/pull/32880#issuecomment-1086905621 concerns were expressed about `dsda-doom` for being "nocross" (I presume it meant not-cross-compatible). 
I'm not sure about this, since maintaining cross-compatibility would be an explicit goal for `dsda-doom` and, indeed, Fabian indicated `dsda-doom` as a successor project, albeit a bit more distant in the actual codebase. 
Even then, should specific compatibility be required in other cases, pretty much all such concerns are covered by `chocolate-doom` and `crispy-doom` (Both already packaged). 

Unless thus `prboomX` is judged worthy of being packaged, and unless an unmainted project of this magnitude is tolerated to stay in repos (It should eventually be update to the latest version, though, in that case), I would say that `prboom-plus` could be safely dropped. 

This is not a request for an update (Although, if `prboom-plus` is allowed to stay even unmainted in repos, it should eventually be updated), just a suggestion/memo/discussion of sorts, since I realize that the situation of Doom Engine-based ports is pretty chaotic, and a few references are needed, especially considered that the idea to drop `prboom-plus` is not mine, as evidenced before. 

Thanks to developers for all their efforts, regardless. 

Re: Suggestion - Drop PrBoom+ (prboom-plus) Now That's Unmaintained And Most Of Its Forks Are Already Packaged

[github-actions]

[-- Attachment #1: Type: text/plain, Size: 293 bytes --]

New comment by github-actions[bot] on void-packages repository

https://github.com/void-linux/void-packages/issues/45051#issuecomment-1762468282

Comment:
Issues become stale 90 days after last activity and are closed 14 days after that.  If this issue is still relevant bump it or assign it.

Re: Suggestion - Drop PrBoom+ (prboom-plus) Now That's Unmaintained And Most Of Its Forks Are Already Packaged

[TeusLollo]

[-- Attachment #1: Type: text/plain, Size: 176 bytes --]

New comment by TeusLollo on void-packages repository

https://github.com/void-linux/void-packages/issues/45051#issuecomment-1763056512

Comment:
Bump, this is still relevant. 

Re: Suggestion - Drop PrBoom+ (prboom-plus) Now That's Unmaintained And Most Of Its Forks Are Already Packaged

[TeusLollo]

[-- Attachment #1: Type: text/plain, Size: 358 bytes --]

New comment by TeusLollo on void-packages repository

https://github.com/void-linux/void-packages/issues/45051#issuecomment-1763056512

Comment:
Bump, this is still relevant. 

Even more so given how the package is reported orphaned: https://github.com/void-linux/void-packages/blob/6b17b6ca0d1dbd2e04009b750bf66f2a726e46f4/srcpkgs/prboom-plus/template#L4

Re: Suggestion - Drop PrBoom+ (prboom-plus) Now That's Unmaintained And Most Of Its Forks Are Already Packaged

[TeusLollo]

[-- Attachment #1: Type: text/plain, Size: 176 bytes --]

New comment by TeusLollo on void-packages repository

https://github.com/void-linux/void-packages/issues/45051#issuecomment-1763056512

Comment:
Bump, this is still relevant. 

Re: Suggestion - Drop PrBoom+ (prboom-plus) Now That's Unmaintained And Most Of Its Forks Are Already Packaged

[github-actions]

[-- Attachment #1: Type: text/plain, Size: 293 bytes --]

New comment by github-actions[bot] on void-packages repository

https://github.com/void-linux/void-packages/issues/45051#issuecomment-1890819332

Comment:
Issues become stale 90 days after last activity and are closed 14 days after that.  If this issue is still relevant bump it or assign it.

Re: Suggestion - Drop PrBoom+ (prboom-plus) Now That's Unmaintained And Most Of Its Forks Are Already Packaged

[TeusLollo]

[-- Attachment #1: Type: text/plain, Size: 332 bytes --]

New comment by TeusLollo on void-packages repository

https://github.com/void-linux/void-packages/issues/45051#issuecomment-1892707279

Comment:
I did not forget about this, btw.

It's just that maintainers forgot to leave behind compiling instructions, hence I'm stuck at getting this compiled. 

Will have to do some digging.

Re: Suggestion - Drop PrBoom+ (prboom-plus) Now That's Unmaintained And Most Of Its Forks Are Already Packaged

[github-actions]

[-- Attachment #1: Type: text/plain, Size: 293 bytes --]

New comment by github-actions[bot] on void-packages repository

https://github.com/void-linux/void-packages/issues/45051#issuecomment-2054528325

Comment:
Issues become stale 90 days after last activity and are closed 14 days after that.  If this issue is still relevant bump it or assign it.

Re: [ISSUE] [CLOSED] Suggestion - Drop PrBoom+ (prboom-plus) Now That's Unmaintained And Most Of Its Forks Are Already Packaged

[github-actions]

[-- Attachment #1: Type: text/plain, Size: 3272 bytes --]

Closed issue by TeusLollo on void-packages repository

https://github.com/void-linux/void-packages/issues/45051

Description:
When `dsda-doom` was packaged at pull https://github.com/void-linux/void-packages/pull/32880, it was suggested by https://github.com/void-linux/void-packages/pull/32880#issuecomment-931756835 to drop `prboom-plus` entirely, although eventually the idea was renounced https://github.com/void-linux/void-packages/pull/32880#issuecomment-1086905621

Well, it appears now that `prboom-plus` is unmainted at https://github.com/coelckers/prboom-plus, and, indeed, the following links confirm that as a matter of fact:

https://doomwiki.org/wiki/PrBoom%2B 
The wiki explicitly lists `prboom-plus` as "discontinued"

https://www.doomworld.com/forum/topic/106866-prboom-2666-jun-20-2023/?page=57 
Fabian, main `prboom-plus` project director, quote for quote, stated the following:

_Hey people,
I'd like to announce that I just tagged the PrBoom+ 2.6.66 release!
https://github.com/coelckers/prboom-plus/releases/tag/v2.6.66
This is just a maintenance release to make the changes that have accumulated over the past 1.5 years available to all users who cannot build the sources themselves. Please do not mistake this as a sign of active development!
Future development will continue to take place in DSDA-Doom [1]. Or, for those who like to stay closer to the original code base, check out JadingTsunami's PrBoomX [2].
[1] https://github.com/kraflab/dsda-doom
[2] https://github.com/JadingTsunami/prboomX_ 

So, it appears they did one last update to v. 2.6.66, but _"do not mistake this as a sign of active development!"_.
`prboom-plus` seems to have been abandoned, thus. 

Now, for its successors, `dsda-doom` is already packaged, while `prboomX` looks like a one-dev project that already shows no signs of active development, thus I personally don't think it's worth it to package it, at least for now. 

At https://github.com/void-linux/void-packages/pull/32880#issuecomment-1086905621 concerns were expressed about `dsda-doom` for being "nocross" (I presume it meant not-cross-compatible). 
I'm not sure about this, since maintaining cross-compatibility would be an explicit goal for `dsda-doom` and, indeed, Fabian indicated `dsda-doom` as a successor project, albeit a bit more distant in the actual codebase. 
Even then, should specific compatibility be required in other cases, pretty much all such concerns are covered by `chocolate-doom` and `crispy-doom` (Both already packaged). 

Unless thus `prboomX` is judged worthy of being packaged, and unless an unmainted project of this magnitude is tolerated to stay in repos (It should eventually be update to the latest version, though, in that case), I would say that `prboom-plus` could be safely dropped. 

This is not a request for an update (Although, if `prboom-plus` is allowed to stay even unmainted in repos, it should eventually be updated), just a suggestion/memo/discussion of sorts, since I realize that the situation of Doom Engine-based ports is pretty chaotic, and a few references are needed, especially considered that the idea to drop `prboom-plus` is not mine, as evidenced before. 

Thanks to developers for all their efforts, regardless.