Status of jed-extra

Rafael Laboissiere rafael at
Fri Sep 30 17:34:23 UTC 2005

* G. Milde <g.milde at> [2005-09-29 16:31]:

> Scope of the jed-extra
> ----------------------
> [...]
>   3. Install a choice of modes (inclusive adding autoloads and
>      add_completion())
>      a) choosen by the packagers
>      b) choosen from a list with debconf
> [...]
> My favourite is 3b, as this allows a good integration into Debian
> and follows Guido Gonzatos "Goccia's Rules of Thumb":

Agreed.  Noticed that debconf is for site-wide configuration, so
draconian choices made by root are imposed on the users.  Anyway, I think
that this is a reasonable solution.

The apache package has a debconf question about which modules should be
loaded when starting the server.  We could take inspiration on it.

Another issue is about abusing debconf.  Normally, debconf questions
should be restricted to only the essential configuration options in the
system.  I think that the default answer is "install everything" and the
priority of the question should be set to "low".

> Contained modes
> ---------------
> Instead of just a download of Jedmodes-CVS, we should offer an
> "intelligent" choice of packages: purge obsolete packages and add
> interesting new ones (most obviously Paul's modes outsoured to separate
> Jedmodes "releases").

Since you are the responsible person for jedmodes, I will let the choice
of packages entirely in your hands.

> Purge dpatches
> --------------
> Most bugfix dpatches are now fixed upstream.

This is good news.  

Now, should we start the implementation of the new jed-extra along the
ideas sketched above?  I will really love to see jed 99.17-111 and the
new jed-extra entering unstable soon.


More information about the Pkg-jed-devel mailing list