After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 743863 - make array returned by g_signal_list_ids sorted
make array returned by g_signal_list_ids sorted
Status: RESOLVED WONTFIX
Product: glib
Classification: Platform
Component: gobject
2.42.x
Other Linux
: Normal enhancement
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2015-02-02 15:28 UTC by marivalenm
Modified: 2015-02-03 09:55 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description marivalenm 2015-02-02 15:28:32 UTC 
Hello,

Is it intentional or coincidental that the function g_signal_list_ids returns an array in random order (probably because of the underlying hash data structure)?

As part of the Debian reproducible build efforts [1] we observed that this behaviour is making some software not build reproducibly. For example all perl packages generating documentation using Glib::GenPod to create pod documentation with lists of used signals. Other users of this function are gstreamer, glade, the python gobject bindings, and the ruby gnome bindings.

Instead of sorting the output of the g_signal_list_ids in all the affected software so that their output is not random anymore, would you consider sorting the output of g_signal_list_ids before returning it?

Kind Regards,
akira

[1] https://wiki.debian.org/ReproducibleBuilds/About
Comment 1 Allison Karlitskaya (desrt) 2015-02-03 09:55:28 UTC 
While I agree with this effort, I'm pretty sure that this is not the correct place to fix the problem.

It is absolutely the concern of the docs generators that things should be in a reasonable order and it surprises me to hear that they just take whatever order pops out of this function.  I'd strongly prefer if the changes were made there instead of here.