On Thu, Jun 13, 2013 at 03:14:04AM -0000, Robert Ancell wrote: > Agree to the concept, however when I have previously looked into this I > haven't come to a conclusion what the correct way of handling this is: > - Should the .d directory to .conf be done inside LightDM, or by the OS / > packaging system?
What gives the best results is if lightdm can parse this itself. Otherwise you have the problem of various files in /etc, some of which are authoritative and can be edited, some of which aren't and will be overwritten. > - What to do when keys conflict? As long as there's a well-defined lexicographical order in which the files are read, and a consistent policy of which key wins (first instance wins vs. last instance wins), I don't think it's a problem. > - What if a program requires a certain combination of keys? Will it still > work if some of them are overridden by another package? Well, presumably all possible combinations of keys should be valid from lightdm's POV, otherwise the keys should be consolidated. :) This feels to me like a problem that can be punted over to any such packages that are requesting contradictory settings, to let them figure it out amongst themselves. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1190425 Title: lightdm should allow packages to override defaults in /etc/lightdm/lightdm.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1190425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
