https://bugzilla.redhat.com/show_bug.cgi?id=1134835 --- Comment #19 from Christopher Meng <i@xxxxxxxx> --- (In reply to David Parsons from comment #18) > (In reply to Pierre-YvesChibon from comment #16) > > (In reply to David Parsons from comment #10) > > > As for point 3. I had read this: > > > http://fedoraproject.org/wiki/Packaging:Guidelines#Libexecdir (files in lib > > > are indeed "executable programs that are designed primarily to be run by > > > other programs rather than by users") but hadn't actually grasped that > > > %{_libdir} would be /usr/lib64 on X86_64. > > > > If the files in %{_libexecdir} are meant to be executed but not by the user, > > then my thoughts are that this folder is appropriate and I don't see the > > need to move them to %{_libdir}. > > If the files are not meant to be executed, then we should look into putting > > them in %{_libdir} > > The files are indeed meant to be executed by a program (not directly by the > user). However, they are not in %{_libexecdir} but in %{_prefix}/lib. This > conforms to FHS and debian packaging guidelines but apparently not quite to > fedora's... Each project has its own way to handle files. And I don't agree with Debian all the time. > Would it be as simple as adding "mv %{_prefix}/lib %{_libexecdir}" somewhere? You can try and checkout to see if it works as its default behavior. Putting something in /usr/lib directly is the fault from upstream as they don't eithor respect the libdir parameter which could be defined during CMake or take into account of /lib64 on some OS, e.g Fedora, RHEL. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review