You are not logged in.
Hi everyone,
I’ve enhanced the "old" ices0 a lot (adding ReplayGain, UTF-8, and lots of other stuff), see https://github.com/Moonbase59/ices0.
I’d like Arch and Arch-based Linux users to easily access this using the AUR, so I wonder how to proceed in this case?
I already tried to flag the existing ices 0.4-1 package as outdated but there was no response.
Would anyone care to maintain this, because I wouldn’t know how?
Thanks for any help!
Moonbase: The Problem Solver. Developer of loudgain (>0.1), StudioDisplay, ices0 (0.4.4+).
Offline
I’ve enhanced the "old" ices0 a lot (adding ReplayGain, UTF-8, and lots of other stuff), see https://github.com/Moonbase59/ices0.
Then it's not (the original) ices0, but some fork. Give it a new name, like eices0 or xices0 (or whatever).
It's also unlikely that somebody else will want to maintain a software, that already exists from a fork with vaguely specified modifications.
Inofficial first vice president of the Rust Evangelism Strike Force
Offline
Thanks for the input, would it be necessary to rename the GitHub repo plus the actual software?
Moonbase: The Problem Solver. Developer of loudgain (>0.1), StudioDisplay, ices0 (0.4.4+).
Offline
Imho no. But the package's name should clarify that it's a fork, that the user is installing.
Inofficial first vice president of the Rust Evangelism Strike Force
Offline
Slightly off topic but https://github.com/Moonbase59/ices0 only starts at v0.4.6 rather than importing v0.4.0 from the xiph svn
then applying ices-cc v0.4.1, v0.4.2 and v0.4.3 as commits from https://centova.com/en/icescc tarballs as I could not find a VCS for those releases
then your own commits on top of that without tracking generated files such as Makefile.in.
Offline
Helpful feedback, @schard & @loqs, thanks! I see there’s still a lot to do … if only I had more time …
Moonbase: The Problem Solver. Developer of loudgain (>0.1), StudioDisplay, ices0 (0.4.4+).
Offline