Github messages for voidlinux
 help / color / mirror / Atom feed
From: github-actions [bot] <"github-actions [bot]"@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Suggestion - Drop PrBoom+ (prboom-plus) Now That's Unmaintained And Most Of Its Forks Are Already Packaged
Date: Tue, 30 Apr 2024 03:45:43 +0200	[thread overview]
Message-ID: <20240430014544.0E8FF22115@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45051@inbox.vuxu.org>

[-- 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. 



      parent reply	other threads:[~2024-04-30  1:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-15 12:32 [ISSUE] " TeusLollo
2023-10-14  1:44 ` github-actions
2023-10-14 17:21 ` TeusLollo
2023-10-14 17:23 ` TeusLollo
2023-10-14 17:36 ` TeusLollo
2024-01-14  1:50 ` github-actions
2024-01-15 19:58 ` TeusLollo
2024-04-15  2:48 ` github-actions
2024-04-30  1:45 ` github-actions [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240430014544.0E8FF22115@inbox.vuxu.org \
    --to=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).