calibre already includes support for .cbr files but needs to find the libunrar.so in order to do so. This file is included in the libunrar0 binary package (which is obviously in non-free): http://packages.debian.org/sid/libunrar0
What I am suggesting is to remove all code in calibre that includes parts of the unrar (non-free) program (are there anyway?) but still leave the support for rar files if the external libunrar.so library is found. This method is dynamic linking, which should not be a problem license-wise, right? Since libunrar is non-free I think the highest dependency it can get in a free package is Suggests. In any case, if you decide to include such a "Suggests: libunrar0" then please let me know and give me a bit of time to upload the newest unrar version which will probably include a rename of the binary libunrar0 (API changed) Hope it is more clear now. Kindest regards, Nick -- =Do- N.AND 2013/6/23 Martin Pitt <mp...@debian.org>: > Hello Nick, > > Nick Andrik [2013-05-22 23:09 +0200]: >> I was refering to the ability to use the unrar backend (already >> packaged in a separate package), not to build the one shipped with >> calibre. >> In order to do this, I think a "Suggests:" libunrar0 would suffice, no? > > What's that "separate package" which contains an unrar backend for > calibre? I don't see anything related. If there is one, shouldn't the > Suggests: be for that one then? > > Martin > -- > Martin Pitt | http://www.piware.de > Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
