Ubuntu

libglib-2.0-dev missplaced files ?

Asked by BytePhunk

hello. while programming for gtk i ran across this situation : apparently for no reason the package installs the file glibconfig.h into this folder :

/usr/lib/glib-2.0/include/glibconfig.h

while any other include files are placed here :

/usr/include/glib-2.0/glib/galloca.h
/usr/include/glib-2.0/glib/garray.h
/usr/include/glib-2.0/glib/gasyncqueue.h
/usr/include/glib-2.0/glib/gatomic.h
/usr/include/glib-2.0/glib/gbacktrace.h

and so on..

that is to say all other includes (all?) are placed in subdirs of /usr/include and this one lies astrayed.
What for ? It gave me a hard time finding it .

Thank you.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Simos Xenitellis 
Solved:
Last query:
Last reply:
Revision history for this message
Best Simos Xenitellis  (simosx) said : 		#1

I do not know if it is put there on purpose.
In such cases, to identify what's going on and to send feedback to the developers so that the problem is fixed, you can do the following,

1. libglib is a GNOME library. The place it is being developed is at
http://svn.gnome.org/viewcvs/
and you can always find the latest source code there.
The package is "glib".
2. When you delve into "glib", you can find the file
http://svn.gnome.org/viewcvs/glib/trunk/Makefile.am?view=log
and in there you can see references to glibconfig.h, and
3. If you click on "View", you can see the latest source code,
http://svn.gnome.org/viewcvs/glib/trunk/Makefile.am?view=markup

and it mentions

configexecincludedir = $(libdir)/glib-2.0/include

which actually means that the file is still installed in the place you mention above.

Ok, how do you communicate with the developers to sort this one one? It might be a mistake on their side, or there might be a reason for it.

View the page with the bug reports for "glib", in case it has been reported already,

http://bugzilla.gnome.org/browse.cgi?product=glib

You can search, or you can check by severity (this should be low severity).
If you did not find it, you can simply file a bug using the link at the sidebar.

I hope the above are useful for you.

Revision history for this message
BytePhunk (bytephunk) said : 		#2

Thanks Simos Xenitellis, that solved my question.