the ebuild has hal[consolekit] in DEPEND if consolekit is enabled, but does actually not depend on it. i removed the line and build gdm without hal installed, i noticed no differences. Reproducible: Always
that is not a valid test nor argument.
what do you mean? if it compiles without hal, it means autoconf is not checking for it. just found this ubuntu bug report: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/418981
added info ...
(In reply to comment #2) > what do you mean? if it compiles without hal, it means autoconf is not checking > for it. > just found this ubuntu bug report: > https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/418981 > But, as I can read in ebuild, hal is in RDEPEND, not in DEPEND, then, it can build without it but maybe some feature is damaged
From what I can see, all the code that actually uses hal is commented out. Found an upstream bug that cleans up the remaining hal-related code from gdm master: https://bugzilla.gnome.org/show_bug.cgi?id=593787 We should be good with just removing the dep (though that will probably trigger "could not connect to hal" warnings). Best to backport the patch. Will try to get to this if nobody beats me to it.
Created attachment 220185 [details, diff] Remove remaining Hal-bits from gdm-2.28 (In reply to comment #5) > We should be good with just removing the dep (though that will probably trigger > "could not connect to hal" warnings). Best to backport the patch. Will try to > get to this if nobody beats me to it. > Is this patch close enough?
I've added a similar path to portage with 2.28.2-r1, thanks for reporting
(In reply to comment #7) > I've added a similar path to portage with 2.28.2-r1, thanks for reporting > I like your take on using rm.:-) Thanks for fixing!