update of jed-extra
G. Milde
g.milde@web.de
Wed Jul 6 12:44:37 UTC 2005
On 5.07.05, Jörg Sommer wrote:
> G. Milde schrieb am Tue 05. Jul, 15:36 (+0200):
> > * Does it make sense to include a "complete" set of modes but not
> > activate/install them? (So people do not need to go to Jedmodes.sf.net
> > or elsewhere.)
> Yes.
OK
> > * Should we use debconf to let the administrator decide which modes to
> > activate/install?
> As a result of the discussion in debian-devel: No.
Well, is there a "sensible default"?
I see two ways of activating:
* the admin copies files to Jed_Local_Library and activates manually
(e.g. by running make_ini()). The mode is then out of Debian control
and will not be updated nor removed by apt-get.
Bad.
* In something that is not debconf, the admin tells jed-extra which
modes to activate.
So why not in debconf?
> > * What core set of modes should be installed (we had this survey
> > already at the time of the first version).
>
> Good question. Can the user do anything if it don't want a mode after we
> have enabled it?
This depends. Assuming update_site_lib() (from make_ini) is used to
activate a mode, the sysadmin could:
* edit ini.sl, or overwrite functions and variables in .jedrc,
--> not really nice.
* delete the mode file(s), and re-run update_site_lib
--> brute force
* modify the Make_Ini_Exclusion_List and re-run update_site_lib().
--> This would not reverse the drop-in replacements with the same
name as standard modes.
The non-root user can only overwrite functions and variables in .jedrc,
--> not really nice.
Günter
--
G.Milde web.de
More information about the Pkg-jed-devel
mailing list