update of jed-extra

[Jörg Sommer]

--RnlQjJ0d97Da+TV1
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

G. Milde schrieb am Wed 06. Jul, 14:44 (+0200):
> On  5.07.05, J=F6rg Sommer wrote:
> > G. Milde schrieb am Tue 05. Jul, 15:36 (+0200):
> > > * Should we use debconf to let the administrator decide which modes to
> > >   activate/install?
> > As a result of the discussion in debian-devel: No.
>=20
> Well, is there a "sensible default"?
>=20
> I see two ways of activating:=20
>  =20
>    * 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.
>     =20
>      Bad.
>     =20
>    * In something that is not debconf, the admin tells jed-extra which
>      modes to activate.=20

     * the admin can set _Jed_Default_Emualtion in jed.conf to the one he
       wants.

>      So why not in debconf?

Because it's simple easy to edit jed.conf or do we talk about
different things?

> > > * What core set of modes should be installed (we had this survey
> > >   already at the time of the first version).
> >=20
> > Good question. Can the user do anything if it don't want a mode after we
> > have enabled it?
>=20
> This depends. Assuming update_site_lib() (from make_ini) is used to
> activate a mode, the sysadmin could:

No I didn't express it exactly. I mean a user who runs jed not the admin.

> The non-root user can only overwrite functions and variables in .jedrc,
>     --> not really nice.

ACK. A way would be to disable loading of jed.conf with command line
option.

We should patch site.sl.

J=F6rg.
--=20
- StGB =A7=A7 328 Absatz 2, Nr.3 : Mit Freiheitsstrafe bis zu
f=FCnf Jahren oder mit Geldstrafe wird bestraft, wer eine
nukleare Explosion verursacht.

--RnlQjJ0d97Da+TV1
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iQEVAwUBQsxGGoZ13Cz2nwVYAQJtTAgAmF8rYkYR0ICPHeQIJi8buIVuCM4sxrD0
KyMs74VQoNjg/AdLRLrLJCvdVQUxvtnjq8v47VhGEuntYYADfwK8XyPM402C06rv
7xn55KjBFbhXviklUKyc6CrppIdpFBRmw1lfjKetHEO2MWtOYBKGypQa3qE9ZkCI
3PGFoYWvEwUD2r6Nsl/r4e/QNTUx2Jt6x6/YNAIK5zEl8+zMjREt1Ri6bH0QCXGu
b7y61yFr0Zkkw0xKZNpPqG2Uq0J6Rw2E0Fvwi6sX8wBSH0D9qpSn8CjArku91DAF
+7uzSDA/zG3BsHe0nyyOK41P/YXFE8ta2HF8MT0eS7csRyc9Szx+cA==
=t/Np
-----END PGP SIGNATURE-----

--RnlQjJ0d97Da+TV1--