Control: forwarded -1
https://gitlab.gnome.org/GNOME/gobject-introspection/issues/323
On Wed, 20 Feb 2019 at 17:03:43 +0100, Helmut Grohne wrote:
> On Sat, Feb 16, 2019 at 05:02:53PM +, Simon McVittie wrote:
> > Multiarch-qualified directories under /usr/share don't seem like they make
> > mu
Hi Simon,
On Sat, Feb 16, 2019 at 05:02:53PM +, Simon McVittie wrote:
> Multiarch-qualified directories under /usr/share don't seem like they make
> much sense: the whole point of the $libdir/$datadir duality is that if
> files need to be different on some architectures, then the files should
On Sun, 17 Feb 2019 at 00:18:54 +0100, W. Martin Borgert wrote:
> (Just for myself in order to not forget it,) the six
> GLib-2.0.gir variants are:
>
> - amd64
> - armel, armhf, i386, mipsel
> - arm64, mips64el, ppc64el
> - hurd-i386
> - mips
> - s390x
>
> The differences are e.g. in how/wh
Hi Simon,
many thanks for taking the time to go through this bug report!
Very much appreciated!
On 2019-02-16 17:02, Simon McVittie wrote:
> Multiarch-qualified directories under /usr/share don't seem like they make
> much sense: the whole point of the $libdir/$datadir duality is that if
> files
(Cross-posting to debian-devel, but with Reply-To to the bug)
On Sat, 16 Feb 2019 at 09:32:16 +0100, W. Martin Borgert wrote:
> at the moment, .gir files are placed under /usr/share/gir-1.0/.
> However, such files can contain architecture specific content.
> What would be the right directory? /usr
5 matches
Mail list logo
