<div dir="ltr"><div><div><div><div><div><div><div><div><div><div>Hello,<br><br>I would like to merge my current CDRtools package [1] in RPMFusion. It currently has quite a large user base. It is used by people who needs to burn Dual Layer DVDs or Blue Ray discs. Currently cdrkit (wodim) is not able to burn them; actually it never had since its first exception.<br>
<br></div>I would like to push the package in both Fedora and EPEL branches; as my package currently works with both. It's also using kernel capabilities in both EPEL 6+ and Fedora; so that's a nice addition to avoid SUID binaries.<br>
<br></div>In its current form it simply replaces wodim and all the other cdrkit packages, so I understand it does not fit in the current RPMFusion policies for package inclusion. I was thinking to adjust it and submit a review.<br>
<br></div></div></div>Cdrkit currently ships with alternatives configured for readcd, cdrecord and mkisofs. The idea is to add a package for shipping those as alternatives for cdrkit with a higher priority. This way, a user who wants to install cdrecord would have the symlink correctly configured with it as the preference; the package would not overwrite base packages and there's no configuration required. And users who don't know what is it, would not get the package.<br>
<br></div>There are a few issues though:<br></div>- Cdrkit ships symlinks for some of the programs, not all (i.e. isoinfo, isovfy, etc.); a bug needs to be opened on cdrkit in Fedora.<br></div>- Cdrtools binaries would have weird names on the system (like cdrtools.cdrecord or cdrtools.mkisofs), but alternatives would return the correct name.<br>
</div><div>- The package gets really complicated for nothing.<br></div><div>- The same cdrkit package shipped in RHEL 6 uses the same alternatives, and bugs in bugzilla gets usually ignored.<br></div><div>- The RHEL 5 package can't be updated, as it already ships cdrecord, etc.<br>
</div><div><br>I think there would be some interest into shipping it in RPMFusion, at least for EPEL 6 and Fedora; what is your idea?<br>Should I proceed into the long process of fixing packages upstream and then publish the review?<br>
</div><div>I have a Redhat account as a customer, so I can probably also file bugs for RHEL 6 cdrkit packages, but I don't know about the results.<br></div></div><div><div><div><div><div><div><div><div><div><div><div>
<br></div><div>Thanks & regards,<br></div><div>--Simone<br></div><div><br>[1] <a href="http://negativo17.org/cdrtools/">http://negativo17.org/cdrtools/</a><br clear="all"><div><br>-- <br><div dir="ltr">You cannot discover new oceans unless you have the courage to lose sight of the shore (R. W. Emerson).<br>
<br><a href="http://xkcd.com/229/" target="_blank">http://xkcd.com/229/</a><br><a href="http://negativo17.org/" target="_blank">http://negativo17.org/</a><br></div>
</div></div></div></div></div></div></div></div></div></div></div></div></div>