Hi Debian, Assistance GNUisances team here :)

We currently have 2 people listed as GNU RCS maintainers: Amin Bandali
and Paul Eggert (both CC'd).  Amin volunteered after Thien-Thi's fatal
accident and Paul seems to have been an RCS maintainer even before
Thien-Thi became one.

A quick glance at the archives of one of RCS mailing lists shows that
at least Paul is still active [1].

[1] https://lists.gnu.org/archive/html/bug-rcs/

For managing hierarchy of files in something like a software project
everyone is likely to pick a modern VCS like Git or Mercurial, I agree.
Nonetheless, I've recently met with opinion that there's no better
single-file VCS than RCS.  So there's at least this niche use case.

Hope this helps.  Best!
Wojtek


--
W. Kosior

website: https://koszko.org/koszko.html
fediverse: https://friendica.me/profile/koszko/profile
PGP fingerprint: E972 7060 E3C5 637C 8A4F  4B42 4BC5 221C 5A79 FD1A


On Fri, 07 Feb 2025 18:45:09 +0100
Romain Francoise <rfranco...@debian.org> wrote:

> Package: wnpp
> Severity: normal
> X-Debbugs-Cc: r...@packages.debian.org
> Control: affects -1 + src:rcs
> 
> I intend to orphan the rcs package. It is in good shape from the Debian
> perspective, however the software itself can now be considered legacy.
> Unfortunately the upstream maintainer passed away a few months ago and
> it's not clear that RCS will be picked up by someone else in the GNU
> project.
> 
> I guess the package could also be removed along with its reverse
> dependencies to no great loss to the project as a whole.
> 
> The package description is:
>  The Revision Control System (RCS) manages multiple
>  revisions of files. RCS automates the storing, retrieval,
>  logging, identification, and merging of revisions. RCS is
>  useful for text that is revised frequently, for example
>  programs, documentation, graphics, papers, and form letters.
>  .
>  Note: this package contains certain general-purpose commands
>  (such as merge or ident) which may used by other programs
>  installed on your system.
> 

Reply via email to