jed-extra: sorting of files into library dirs

[Jörg Sommer]

Hello G.,

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

>   (Alternatives: /usr/share/jed/site-lib/, /usr/share/jed/jed-extra-lib/)

I would prefer the last one.

> * 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/
>   
>   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.

>   * 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.
> 
> Alternatively, all files could go to /usr/lib/jed-extra/ and the dir be
> *added* in 50jed-extra.sl with a comment a'la::

No. I find your first idea really good. We should take it.

> > >   I could provide a slang script that does this based on a list of modes
> > > (now in README.Maintainer). Alternatively, this sorting could be done in the
> > > rules file. However, I have no experience with rules files and thus would be
> > > very inefficient in modifying it.
> > 
> > The rules file is a simple make file, nothing more.
> 
> I already guessed. However, I never worked with a make file :-(

Would you modify the build-orig.tar_gz? Maybe you can check if all modes
provides a licence note and we can remove the licence stuff from
build-orig.tar_gz. How would you separate the modes? Due to
README.Maintainer?

Bye, Jörg.
-- 
NetBSD ist für Frauen: es läuft auf Waschmaschinen
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 481 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-jed-devel/attachments/20051013/d4609d52/attachment.pgp