[Pkg-jed-devel] Re: do not load jed.conf

[Rafael Laboissiere]

* Rafael Laboissiere <rafael@debian.org> [2005-04-22 16:54]:

> * Paul Boekholt <p.boekholt@hetnet.nl> [2005-04-22 14:21]:
> 
> > Presumably jed-sl includes the slang sources.  Is there any reason for
> > including .slc and .dfa files as well?  When I switched from slang 1 to
> > slang 2, I had to remove all my .slc files.  After that I haven't
> > byte-compiled, but I don't rule out that a .slc file compiled with
> > slang 2 pre 7 doesn't work with slang 2 pre 8, etc.  So I think you
> > should do any byte-compiling in the install script, which would also
> > make the package smaller of course.
> 
> Building the .slc files at install time is indeed a good idea.  BTW, the
> (X)Emacs packages in Debian use this approach to build the .elc.  We
> might implement this for the the jed-common Debian package.

I have thought a little bit further about this.  The way the Debian packages
are are organized is as follows:

    - jed and xjed contain the the executables for terminal and X11, viz.
    - jed-common contains all the *.slc files generated at build time
    - jed-sl contains all the *.sl files for which there are *.slc files
    
If we implement the "build at install time" idea from Paul, we will have
to include the *.sl files in jed-common.  This will force us to eliminate
the jed-sl package.  Also, the "smaller size" argument would be moot,
because the *.sl files are actually larger than the corresponding *.slc
files.

I already started experimenting with the postinst and prerm scripts in the
jed-common package.  Should I go already with this idea?  In this case, we
should revert the NO_JED_CONF changes done by Jörg.

What do you guys think.
 
-- 
Rafael