On Wed, Feb 16, 2011 at 09:49:09AM +0000, Emmanuele Bassi wrote:
> On Wed, 2011-02-16 at 09:42 +0100, David Nečas wrote:
> > On Wed, Feb 16, 2011 at 08:20:59AM +0000, Emmanuele Bassi wrote:
> > > in any case, this is a pointless discussion: the schema for the file
> > > chooser configuration *is* part of the gtk+-3 installation; if it's not
> > > installed then it's either a bug in gtk+ or a packaging issue. it's the
> > > equivalent of an header file, or a module provided by gtk+ itself.
> >
> > Gtk+ itself (not any dependency) installs this scheme file.
> > It knows exactly, at compile time, where the file will be installed.
> > So why it cannot find the file?
>
> it could be that XDG_SHARE_DIR is unset, or not set to include your
> $prefix/share.
Well, this describes the mechanism how it happened but does not answer
why. If you read the question
It knows exactly, at compile time, where the file will be installed.
So why it cannot find the file?
it makes sense whether any XDG-foo gets involved or not. The question
is why something that is both perfectly reasonable to expect do work and
very easy to make work does not work? Why it is intentionally broken?
A package that requires to set some environment variables after
installation to tell it where its parts were installed (if nothing has
been moved elsewhere!) is broken. There's no other word for it.
If the corresponding freedesktop standard *forbids* Gtk+ from just
working then this standard is broken and needs to be ammended/ignored.
Yeti
_______________________________________________
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
