On Wed, Apr 8, 2015 at 8:50 PM, Marc-Antoine Perennou
<marc-anto...@perennou.com> wrote:
> Well, on one hand, we may have the need for multilib stuff to find the
> native binaries, as you said.
>
> On the other hand we have my case. Just a bit of background so that
> you understand where these patches come from:
> I'm developper for the Exherbo distribution, and we recently changed
> completely our filesystem layout when we introduced full
> cross-compilation support.
> We now have everything in /usr/arch (when you put stuff into /usr/lib/arch).
> We thus have complete trees for each arch with
> /usr/arch/{bin,sbin,lib,libexec,include} and want those to be
> completely independant.
> We try to keep as vanilla as possible and I think we're quite good at
> it, but inevitably we reach corner cases where it's impossible.Yeah, that all makes sense. And we can have both. :) > If you think it might make sense to have everything in > libdir/pkgconfig (depite the redundancy of information), I'd be very > happy. > If instead you go and put everything into /usr/share/pkgconfig, it > won't hurt that much for us to keep this patch downstream. Right, we have to find out what we want to support here, cross-compile or secondary arch things. Only one thing is clear at the moment, that the current status makes no sense. :) We got $libdir for the secondary arch: http://cgit.freedesktop.org/systemd/systemd/commit/?id=eb39a6239c631873db62f6a942e6cb3dab0a2db4 But then we took $libdir as the reason to move the file and make it inaccessible for the secondary arch: http://cgit.freedesktop.org/systemd/systemd/commit/?id=aec432c6134146e138124c4130be2ee89dca07fa Kay _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
