[arch-dev-public] Dropping cdrkit, replacing with cdrtools
Since we're dropping dead packages, I have one package remaining on the "missing sources" todo list: cdrkit. Given the fact that Debian has forked an old cdrtools release, applied some patches and then abandoned the project completely, I would like to remove it and replace it with the original software which is still developed. cdrtools is already in community, so it only needs a move to extra. It's already a drop-in replacement for cdrkit, so we can handle the dependencies later. Last note: only thing that keeps me from moving this right now is the maintenance. The current maintainer in community has maintained this package for 5 years with regular updates and does a good job maintaining his packages. It would be nice if he could continue maintaining the package, but I think it's good to have mkisofs and cdrecord in extra instead of community. Any thoughts about this?
[2017-01-21 00:39:52 +0100] Jan de Groot:
Since we're dropping dead packages, I have one package remaining on the "missing sources" todo list: cdrkit.
Given the fact that Debian has forked an old cdrtools release, applied some patches and then abandoned the project completely, I would like to remove it and replace it with the original software which is still developed.
Sounds good to me.
cdrtools is already in community, so it only needs a move to extra. It's already a drop-in replacement for cdrkit, so we can handle the dependencies later.
Last note: only thing that keeps me from moving this right now is the maintenance. The current maintainer in community has maintained this package for 5 years with regular updates and does a good job maintaining his packages. It would be nice if he could continue maintaining the package, but I think it's good to have mkisofs and cdrecord in extra instead of community. Any thoughts about this?
It really makes no difference if mkisofs and cdrecord (or most packages for that matter) are in [community] rather than [extra]. Cheers. -- Gaetan
On 21 January 2017 at 00:39, Jan de Groot <jan@jgc.homeip.net> wrote:
Last note: only thing that keeps me from moving this right now is the maintenance. The current maintainer in community has maintained this package for 5 years with regular updates and does a good job maintaining his packages. It would be nice if he could continue maintaining the package, but I think it's good to have mkisofs and cdrecord in extra instead of community. Any thoughts about this?
If you think cdrecord would be better off in [extra] I'm OK with moving it and someone else taking over. If it stays in [community] I have no issue maintaining it either, it's a low-maintenance package. Lukas
participants (3)
-
Gaetan Bisson
-
Jan de Groot
-
Lukas Jirkovsky