Hi, I'm unsure what I should do with the following bug, so I'm asking here for advice (especially since I know Hamish Moffatt and Ben Gertzfield read this list, since their www-mysql and libdbd-mysql-perl packages might be affected).
Up to now, I've been following the upstream source and installing subdirectories /usr/include/mysql and /usr/lib/mysql for header files and static libraries. Last month I received the following bug report: Brian White <[EMAIL PROTECTED]> writes: > Package: mysql-dev > Version: 3.21.25gamma-1 > > This package puts all the .a libraries under /usr/lib/mysql. The > standard place for these is simply under /usr/lib. If the library > names are too general, then perhaps they should be renamed? > > Also, packages are now installing their include files directly under > /usr/include instead of /usr/include/subdir. You should probably > move (at least the main include file) directly under /usr/include. Is this policy? I checked the policy manual and the fhs docs, but I couldn't find any clear answers. There are no other packages in hamm that put .a libraries into a subdirectory. I'd be inclined to simply take Brian's advice and move the files, but the upstream configure/Makefile.PL scripts for www-mysql and libdbd-mysql-perl expect to find mysql subdirectories for these files. Also, moving the files would break things like '#include <mysql/mysql.h>' (although I could only find one instance of that in packages that need mysql-dev to compile). I also checked the competition :) the mysql-dev rpm package keeps the subdirectories. Should I move the files, or leave them where they are? Any words of wisdom would be welcome. Thanks, Scott -- Scott Hanson <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Johmsweg 9, D-21266 Jesteburg, Germany -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
