Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
View Bug Activity | Format For Printing | XML | Clone This Bug
The build scripts for cdrtools will detect the presence of the acl libraries and use them automatically. However, this leads to dependencies that Portage doesn't know about, so I suggest that the use of acl be controlled by a USE flag. Reproducible: Always Steps to Reproduce: 1.install sys-apps/acl 2.install cdrtools 3.remove sys-apps/acl Actual Results: cdrtools has missing dynamic links Expected Results: a warning when sys-apps/acl is unmerged I'll upload a patch for this. It may need some cleaning up, as I am not an ebuild expert.
Created an attachment (id=135718) [edit] Adds "with-acl" and "without-acl" options to the configure script.
Created an attachment (id=135719) [edit] Adds 'acl' USE flag to cdrtools ebuild
cdrtools-2.01.01a36 has some changes according to ACL (see ftp://ftp.berlios.de/pub/cdrecord/alpha/AN-2.01.01a36). Probably your patch is not needed any more on that version. Furthermore you check for 'acllib.h' in your patch (actually, cdrtools check for that file as well), but this one does not get installed by sys-apps/acl. So your patch will always fail. On the other hand I try to keep cdrtools as unpatched as needed, as it seems to be a fragile framework for patches. Especially when you need support from upstream and use a heavily patched version. So I'm more in favour of adding sys-apps/acl as a hard dependency rather than creating a patch and test for the existance of those header-files.
(In reply to comment #3) > cdrtools-2.01.01a36 has some changes according to ACL (see > ftp://ftp.berlios.de/pub/cdrecord/alpha/AN-2.01.01a36). Probably your patch is > not needed any more on that version. > > Furthermore you check for 'acllib.h' in your patch (actually, cdrtools check > for that file as well), but this one does not get installed by sys-apps/acl. > So your patch will always fail. > > On the other hand I try to keep cdrtools as unpatched as needed, as it seems to > be a fragile framework for patches. Especially when you need support from > upstream and use a heavily patched version. So I'm more in favour of adding > sys-apps/acl as a hard dependency rather than creating a patch and test for the > existance of those header-files. > Agreed, added to cdrtools-2.01.01_alpha36-r1.ebuild
Is there any chance the hard ACL dep could be discussed with (and the patch approved by) upstream devs? Thanks