Unmaintained, abandoned upstream, depends on an outdated version of
the abandoned libav, and doesn’t build even if that dependency is
replaced with FFmpeg.
game-music-emu needs to be in LD_LIBRARY_PATH for the app to find it.
gst-python and pylyrics are no longer used.
tauon does have optional support for libjxl, but it's via the python
library pyjxl and not directly with the C library.
If the interpreter path to bash after patchShebang contians the string
'gcc', then we will end up mangaling the shebang interpreter path with
the substituteInPlace on 'gcc' that follows the patchShebang.
We can fix this by switching the order of the two, but since this script
is only used once during compilation, it's simplier just to call bash
directly to run the script.
While preparing this change, I read the git blame on all of the files I
touched. I saw a working lifetime of building this system which we use
every day and love dearly and keep maintained ourselves. I saw commits
from a 14 year range between 2003 to 2017!! I could not be more thankful
for Eelco's work on building large parts of the foundation of nixpkgs
that all of us rely on now.
However, the end date of that range of the files I looked at the blame
on was 2017. I did not see surviving code from any newer date than that.
Looking at the Git logs, Eelco has been working on other things, and
that's totally fine.
However, it means that our maintenance metadata is out of date on a lot
of packages, and *that*'s the reason I am submitting this change. There
are a lot of packages that don't have anyone with their name on them to
be pinged if they need attention, even if they have had recent activity
(although it is never clear if recent activity was just someone fixing
it because ZHF or because the package actually matters to them).
There are a lot of packages with storied history that maybe don't need
to be in the set anymore at all since they have not been touched in
years; or maybe they are simply finished.
Empty maintainer lists should be a sign that we need to figure out who
maintains it or potentially remove it if it has rotted, and allowing the
maintainer list to be empty if it is already not maintained is part of a
healthy repository ecology.
Either way, I would like to have the maintenance metadata not mislead
anyone into sending Eelco emails about packages he doesn't, in practice,
work on anymore. I have not removed his name from everything; there are
some things that he is the upstream for or has worked on more recently,
for instance, like Nix, which I have left alone.
