<p dir="ltr"><br>
Am 31.12.2014 12:54 schrieb "Simon Peeters" <<a href="mailto:peeters.simon@gmail.com">peeters.simon@gmail.com</a>>:<br>
><br>
> 2014-12-31 11:12 GMT+00:00 Martin Pitt <<a href="mailto:martin.pitt@ubuntu.com">martin.pitt@ubuntu.com</a>>:<br>
> > Simon Peeters [2014-12-29 15:01 +0000]:<br>
> >> I have no preference between the 2, but moving the pc file to<br>
> >> $libdir/pkgconfig just does not make sense.<br>
> ><br>
> > Why not? pkg-config looks in both /usr/share and /usr/lib, so it<br>
> > doesn't care. And you can't install systemd for multiple architectures<br>
> > in parallel anyway, so you'd only ever have one version installed.<br>
><br>
> Let me rephrase what I wrote above that quote:<br>
><br>
> If I understand lennarts commit message, the only reason for libdir to<br>
> be in the pc file is to find the libdir for the primary arch.<br>
> moving this pc file into $libdir/pkgconfig would require you to know<br>
> the libdir for the primary arch (or at least the one systemd was<br>
> compiled for) in order to read it</p>
<p dir="ltr">I don't think this is true. Usually one doesn't parse .pc files directly but instead you use pkg-config. So you don't need to know the libdir for the primary arch. <br>
</p>