Reply To: patched gksu + libgksu available

[Anonymous]

Here are some additional changelog notes for the next version.
Posting these because I realize that my changes may not be amenable to y’all
~~ for antiX distribution you might want to just revert to the stock (before my meddling) gksu code.

  * removed "gksu-properties" chooser GUI utility
  * gksu.schemas.in: specify default value "true" for
       <key>/schemas/apps/gksu/sudo-mode</key>
  * debian/gconf-defaults.libgksu-su:
       specify "/apps/gksu/sudo-mode true"
  * dropped inapplicable 01_tcdrain_kfreebsd.patch
  * merged 02_format-security.patch
  * merged 03_makefile_spaces.patch
  * merged 04_automake.patch
  * merged 05_ja.patch
  * merged 06_unguarded_child_stderr.patch
  * merged 13_startup_notification.diff
  * merged 14_polish_startup.diff
  * merged 18_g_markup_escape_text_for_command.patch
  * merged 22_sudo_keep_env.patch
  * merged 23_correct_colormap_get.patch
  * merged 24_cross.patch
  * merged 27_sudo_wrong_pwd_check.patch
  * merged 29_check_newline.patch
  * merged 99_intltool.patch
  * removed redundant debian/pos/pt_BR.po
  * edited debian/README.Debian
       toward (hopefully) rendering it somewhat less nonsensical
  * REMOVED the debian trickery described within debian/README.Debian
       and renamed that file debian/README.Debian_obsolete.
       Removed calls to "update-alternatives" from postrm, prerm, postinst

Removal of “gksu-properties” will necessitate axing an item from antixcc.sh

The rationale for its removal is that gksu is (has been) provided soley to cover the “use case”
of crafting convenient sudo_mode “elevated permissions” launchers.

Regarging the debian-specific muckery:

Unless someone has inspected the contents of the source package and read debian/README.Debian
there’s slim chance that anyone, including the local sysadmin, could determine WHICH END IS _UP_

==================
libgksu for Debian
==================

The gksu library enables the user to run programs with root powers
using one of su or sudo as backend. If the application that uses
the library doesn't specify the backend it wants to use, the backend
will be selected through the '/apps/gksu/sudo-mode' boolean gconf option.

The Debian package provides two gconf default files, one of them
setting sudo-mode to true, the other setting sudo-mode to false. Which
one of them is used to set the default is decided through an alternative.

Debian tools, Systems Administrators and custom distributions builders
might want to make use of this functionality to decide whhich backend
to use. This is done by configuring the libgksu-gconf-default alternative:

 # update-alternatives --config libgksu-gconf-defaults

 There are 2 alternatives which provide 'libgksu-gconf-defaults'.

   Selection    Alternative
 -----------------------------------------------
 *         1    /usr/share/libgksu/debian/gconf-defaults.libgksu-sudo
  +        2    /usr/share/libgksu/debian/gconf-defaults.libgksu-su

 Press enter to keep the default[*], or type selection number: 2
 Using '/usr/share/libgksu/debian/gconf-defaults.libgksu-su' to provide
 'libgksu-gconf-defaults'.

After setting the alternative you must run the 'update-gconf-defaults'
script to actually apply the setting to the gconf defaults XML file.

While this possibility exists, it would be best if it is only used by
the internal Debian infra-structure, since there are already better
and documented ways of providing "default" settings for gconf-using
applications both in the upstream software[0] and in the gconf
packaging[1] itself, good for administrators and custom distributions
builders, respectively.

[0]: Read the GNOME Desktop System Administration Guide at
     http://www.gnome.org/learn/admin-guide/latest/
[1]: See the dh_gconf(1) script provided in the debhelper package and
     also see the /usr/sbin/update-gconf-defaults python script
     provided in the gconf package

 -- Gustavo Noronha Silva <kov@debian.org>, Sun,  3 Sep 2006 19:06:47 -0300

On a pristine antiX17 system, if you checked
update-alternatives –config libgksu-gconf-defaults
v— the result doesn’t exactly match those (hidden, and outdated) source docs

=======================================================
 There are 2 alternatives which provide 'libgksu-gconf-defaults'.

   Selection    path_of_Alternative                         Priority    Status
 ----------------------------------------------------------------------------------
 * 0  /usr/share/libgksu/debian/gconf-defaults.libgksu-su     20        auto mode
   1  /usr/share/libgksu/debian/gconf-defaults.libgksu-sudo   20
   2  /usr/share/libgksu/debian/gconf-defaults.libgksu-su     10

 Press enter to keep the (current choice, aka) default[*], or type selection number: 2
========================================================

.
cd /usr/share/doc && find -iname README.Debian | grep ‘gksu’
man gksu

Nope, this too-clever nonsense is not disclosed in the installed docs.

After setting the alternative you must run the ‘update-gconf-defaults’
script to actually apply the setting to the gconf defaults XML file.

Who knew this?!? Go ahead, raise your hand…

.
.
.
update-alternatives –config libgksu-gconf-defaults
So… as noted in the changelog (“REMOVED the debian trickery”)