FS#46114 - [cdrkit] upstream (website?) dead
Attached to Project:
Arch Linux
Opened by Sebastiaan Lokhorst (lonaowna) - Wednesday, 26 August 2015, 17:00 GMT
Last edited by Jan de Groot (JGC) - Sunday, 22 January 2017, 19:03 GMT
Opened by Sebastiaan Lokhorst (lonaowna) - Wednesday, 26 August 2015, 17:00 GMT
Last edited by Jan de Groot (JGC) - Sunday, 22 January 2017, 19:03 GMT
|
Details
The upstream website cdrkit.org is dead. It is impossible to
get the source, and the website seems to be down for almost
a year now.[1]
I'm not really familiar with the project, so I don't know if it has moved or the project is really dead. In any case, it would be nice to be able to build the package myself, so if there is no alternative upstream location available and assuming we will keep offering the package, could we host the source ourselves? [1] http://web.archive.org/web/*/http://www.cdrkit.org/ |
This task depends upon
Closed by Jan de Groot (JGC)
Sunday, 22 January 2017, 19:03 GMT
Reason for closing: Fixed
Additional comments about closing: cdrkit removed
Sunday, 22 January 2017, 19:03 GMT
Reason for closing: Fixed
Additional comments about closing: cdrkit removed
I think we should try cdrskin from libburn as a cdrecord replacement. But how do the other distributions handle this currently?
But, if libburn/cdrskin is equal or better, then I can see why that would be preferable, circumventing the potential issues completely.
Having cdrtools in community nullifies the whole reason why cdrkit was packaged in the first place.
I don't have experience with cdrskin, but looking at the cdrkit debacle (tonnes of bugs, no fixes, no maintenance) I don't like going for an emulated or forked version of such a common tool as cdrecord/mkisofs.
IMHO we should just drop cdrkit and package cdrecord instead. If there's any real license problem here Joerg should deal with it.
I'm not sure about cdrskin either, but it's always good to have an alternative (and we already package it anyway).
My recommendation: Drop cdrkit and put cdrtools back in place. It saves money and avoids frustrations.
Debian has a copy of upstream or modified-upstream saved as "*.orig.tar.*" file. RHEL and derivatives also have *.src.rpm files which includes upstream tarball and .spec file.
Learning from those big distribution, Arch Linux infrastructure should also have a copy of upstream source tarball to avoid being unable to rebuild (in case of C / C++ abi changes, etc) package just because of dead upstream website.
For now, it may be just fine to point to "http://httpredir.debian.org/debian/pool/main/c/cdrkit/cdrkit_1.1.11.orig.tar.gz" as cdrkit source.