On Wed, Jan 17, 2007 at 11:31:15AM +0100, Ludwig Nussel wrote:
> Ok. However, pkgconfig files typically specify -L${libdir} in their linker
> flags which would result in -L/lib. So I guess it would actually make more
> sense to run configure with %_libdir and then move non-devel files to /lib
> instead of the other way around.It depends on what your package actually contains: - If your package only contains a library you might be right: If you install to /lib first, then you have to move only the include files, the static libs (if any) to /usr/lib and recreate symlinks in /usr/lib. If you install in /usr/lib first then you have to move the shared libs to /lib and also recreate the symlinks in /usr/lib (because they have to point to a different location then). So in this case you might save a bit of moving but the most complex part (recreating the symlinks) did not change. - If your package does contain executables or data es well, everything turns the other way around: First you have to move the binaries as well with your proposal and second there is the problem that the build might encode the (wrong!) path to the binaries where the data is found, leading to the result that the tool can no longer find it's data after moving it. Robert -- Robert Schiele Dipl.-Wirtsch.informatiker mailto:[EMAIL PROTECTED] "Quidquid latine dictum sit, altum sonatur."
pgpo4r1MyUkwn.pgp
Description: PGP signature
