Bug#382670: debian-installer: Sudo not properly configured
Em Wed, 23 Aug 2006 02:29:27 -0400
Joey Hess <joeyh@debian.org> escreveu:
> If the schema file is managed by alternatives, I think it would be
> better to let d-i detect this case and switch to the sudo
> alternative. Users can choose to use a sudo-only setup in expert mode
> so a hidden question isn't the best approach.
Indeed! I am now better informed, after asking the rest of the GNOME
team and doing some research.
So, we have two options and I would like to count with your experience
on deciding which one is best:
====================
Using an alternative
====================
I install two gconf defaults files, one containing this (save the
markers):
-- begin
/apps/gksu/sudo-mode false
-- end
The other one this:
-- begin
/apps/gksu/sudo-mode true
-- end
Installing an alternative to the path actually used
by /usr/sbin/update-gconf-defaults; The drawback here is we need to be
careful to always call update-gconf-defaults after setting this
alternative.
=============================
d-i installs an override file
=============================
Prior to the installation of libgksu2-0 d-i installs a file
called 11_libgksu2-0 to /usr/share/gconf/defaults/ containing the
follwing:
-- begin
/apps/gksu/sudo-mode true
-- end
The only change to the libgksu2-0 package (which is the responsible for
the gconf stuff and does all the gksu magic these days) is making it
call update-gconf-defaults. Another option would be to do nothing to
the libgksu2-0 package and have d-i call that script itself, which
removes the 'Prior to the installation' requirement.
The number 11 seems like the best choice; priority 10 is for the
package to use, the [20-50[ range is for derived distributions and the
[50-...] range for CDDs according to dh_gconf's manpage. We could use
15 as well, and leave [11-15[ for other packaging tricks that may be
necessary.
This way, when libgksu2-0's postinst is called the 11_libgksu2-0 setup
will override the one distributed by the package and we're set. I'd
even suggest that this is done regardless of libgksu2-0 being installed
in the d-i install process, so that if the user decides to install
gksu or some other thing that uses libgksu2-0 later on, the defaults
are already sane.
Both solutions sound simple, and require only minor intervention in the
package; I cannot say what's best for d-i, though, since I'm not
up-to-date with how it is working. I don't know, for instance, if the
installer is allowed to install files to /usr/share itself to modify
package behavior like this.
Whatever you say, I plan to implement it this week (this weekend if
possible =)).
Abraço,
--
Gustavo Noronha Silva <kov@debian.org>
http://people.debian.org/~kov/
Reply to: