jed-extra: sorting of files into library dirs

[G. Milde]

Hi Jörg,

On 13.10.05, Jörg Sommer wrote:
> G. Milde schrieb am Wed 12. Oct, 15:59 (+0200):
> > Where should the modes go?
> > --------------------------
> > 
> > * Generally, modes should go to the `jed-extra library directory` ::
> > 
> >         /usr/lib/jed-extra/
> 
> /usr/lib/ is wrong. It must /usr/share, because we have architecture
> independent data. -> FHS

I see. 

> >   (Alternatives: /usr/share/jed/site-lib/, /usr/share/jed/jed-extra-lib/)
> I would prefer the last one.

How about /usr/share/jed/site-lib/jed-extra/ ?

  * jed-common should set up (and append to the library path) site-lib/
    as place where Debian packages can put jed extensions.
    
  * a package that provides just one mode simply puts it there  
  
  * jed-extra creates a subdir, so that
  
      - site-lib/jed-extra/ can be *appended* or *added* in 
        jed.d/50jed-extra.sl
        
      - if the sysadmin chooses not to register site-lib/jed-extra/,
        autoloads and require() can use the relative path as e.g.
           autoload("locate", "jed-extra/filelist");
        (this is not possible with /usr/share/jed/jed-extra-lib/)

 
> > * Some modes are drop-in replacements. Placing them in the jed_library_path
> >   would either
> >    
> >   a) make their use obligatory for all users if the libdir is *added*, or
> >   b) prevent their use if the libdir is *appended*.
> > 
> >   Drop-ins should therefore go to a separate dir, say ::
> >   
> >         /usr/lib/jed-extra/drop-in/

now either
             /usr/share/jed/site-lib/jed-extra/drop-in/
or (my pref)
             /usr/share/jed/site-lib/drop-in/

> >   *added* to the library path in 50jed-extra.sl.
> 
> Why not add a debconf question to let the admin decide, if the path is
> added or appended? OTOH, it is not trivial to edit the 50jed-extra.sl
> file with the postinst script and call debconf on every jed startup takes
> to long.

This would be both, complicated to realize and possibly a debconf abuse (as
this decision is not necessary for the working of the package).
The admin can change the default by editing 50jed-extra.sl, a note in
README.Debian will point this out. This is IMHO both easy to implement and
something one could expect from a Debian package.
 
> >   * The default behaviour would be to use the drop-ins if jed-extra
> >     is installed
> >   * A sysadmin can easily comment out the activation of drop-ins
> >   * A user can remove the drop-in/ dir from the library path in jed.rc
> >     (a function remove_libdir() in libdir.sl could assist)  
> >   * Fine-grained activation of drop-ins is possible by copying or symlinking
> >     of individual modes to a users (or local) libdir.
        
        .. or with a set of specific autoloads(..., drop-in/...);
 
 
> Would you modify the build-orig.tar_gz? 

If I had to do it, I would replace it with a SLang script.

> Maybe you can check if all modes
> provide a licence note and we can remove the licence stuff from
> build-orig.tar_gz. 

The only file with problems now is email.sl (see the discussion with Paul).
Francesc Rocher, Johann Gerell, and Kyle Wheeler gave me the explicit
permission to add a GPL license notice to all their modes.

> How would you separate the modes? Due to README.Maintainer?

I would save the list now in README.Maintainer into a separate file and
parse this.

Guenter

-- 
G.Milde web.de