Re: Roadmap for 0.99-17

["G. Milde" <g.milde@xxxxxx>]

On 12.09.05, John E. Davis wrote:
...
 
> There are several other minor issues that I would like to see resolved
> or at least documented for 0.99-18.  These include:

...

>    3.  The issue of the conditional loading of jed.conf.  A
>        commandline switch has been proposed but I simply am unable to
>        see why this is necessary.  Is there a concrete example that
>        illustrates why the loading of jed.conf should be conditional?

The real world example that triggered the discussion on pkg-jed-devel is
described in 
http://lists.alioth.debian.org/pipermail/pkg-jed-devel/2005-April/000034.html

   It's a "bootstrap problem". Building a new version of jed failed
   because some code in jed-init.d (loaded by Debian's /etc/jed.conf)
   depended on stuff not available on this stage. 
   
   Disabling the evaluation of jed.conf seemed to be the cleanest
   solution (especially, as there is already the -n option to disable the
   personal configuration file).

However, the problem seems to be Debian specific, so it might be better
solved by a Debian patch.  Actually, the Debian SVN version patches
site.sl to evalutate all *.sl files in /etc/jed-init.d/ instead of
/etc/jed.conf (to not pollute /etc/ with 2 jed-specific entries).

So I withdraw my feature request.


BTW: May I remind you to look into the Default_Jedrc_Startup_File problem
(is loading JED_ROOT/lib/jed.rc when there is no ~/.jedrc really needed)?

My suggestion would be either to change

-public variable Default_Jedrc_Startup_File = "jed.rc";
+public variable Default_Jedrc_Startup_File = NULL;

or (preferabely) remove the Default_Jedrc_Startup_File variable completely
(as system-wide settings could be done in defaults.sl or jed.conf).


Günter

-- 
G.Milde web.de

--------------------------
To unsubscribe send email to <jed-users-request@xxxxxxxxxxx> with
the word "unsubscribe" in the message body.
Need help? Email <jed-users-owner@xxxxxxxxxxx>.