2014-12-31 11:12 GMT+00:00 Martin Pitt <martin.p...@ubuntu.com>: > Simon Peeters [2014-12-29 15:01 +0000]: >> I have no preference between the 2, but moving the pc file to >> $libdir/pkgconfig just does not make sense. > > Why not? pkg-config looks in both /usr/share and /usr/lib, so it > doesn't care. And you can't install systemd for multiple architectures > in parallel anyway, so you'd only ever have one version installed.
Let me rephrase what I wrote above that quote: If I understand lennarts commit message, the only reason for libdir to be in the pc file is to find the libdir for the primary arch. moving this pc file into $libdir/pkgconfig would require you to know the libdir for the primary arch (or at least the one systemd was compiled for) in order to read it, so the libdir variable in the pc file is redundant because the information it contains needs to be known in order to read it. So if you would move the pc file to $libdir then the libdir variable in the pc file no longer has any purpose, so you can drop it. Now you have a pc file in libdir without any architecture specific data, so you could as well move it back to /usr/share But anyway, that is only if I understand the purpose of the libdir var in the pc file correctly. Greetings. (and enjoy the end of 2014!) Simon _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
