[Pkg-jed-devel] error building jed_0.99.16.pre.0.99.17.84-1

[G. Milde]

On 15.04.05, Jörg Sommer wrote:
> G. Milde schrieb am Fri 15. Apr, 15:17 (+0200) :
> > On 15.04.05, Jörg Sommer wrote:
> > > I would prefer:
> > >
> > > if (getenv("NO_JED_CONF") == NULL)
> > >   do_jed_conf();
> > 
> > % debian jed.conf as suggested by John E. Davis
> > % Read the documentation in /usr/share/doc/jed-common/README.Debian-startup.
> > % Please do not change this if you want the documented debian startup system
> > % to function correctly.
> > 
> > if (getenv("JED_SKIP_INIT_D") != NULL)
> > {
> >  $1 = listdir ("/etc/jed-init.d");
> 
> This was also my idea, but it doesn't work. We can't manipulate the
> jed.conf of the current installed version. The only way is, to prevent it
> from coming up.

Unfortunately, I do not see a way to prevent jed.conf from coming up in the
installed version (as I suppose we cannot manipulate site.sl either).

However, we could try to eliminate the bug for the more-than next
versions by providing a means to skip jed_init.d in jed.conf of the next
jed package.


It seems the "command line argument approach" got a consensus.

IMHO, we should 

* consider, whether we want prevent:

    evaluating files in jed_init.d
  or
    evaluating jed.conf  


* ask J E D for his advice and suggest a new command line argument to
  him, so it could possibly be incorporated into site.sl of a new 
  jed release. (remember, /etc/jed.conf is already an extension due to the
  request of the then Debian maintainer)
  
* if John doesnot like a new command line arg just for Debian, we could
  still "emulate" it in jed.conf by looking at __argv and killing the
  spurious "argument buffer". As this argument is rather seldom used, the
  overhead of the spurious buffer would not seriusly harm.

  
 
> And the same problem would occure with /u/l/etc/jed.conf and
> /u/etc/jed.conf. We can't change any of this files while building and
> they all make the build fail, because their expected files aren't in the
> path.

Do you mean /usr/local/etc/jed.conf and /usr/etc/jed.conf?

AFAIK, these two were never used by Debian, so a Debian package doesnot
need to take of them explicitely. (However, documentation to a possible
"Debian-only" command line arg should make clear it does not touch the
handling of them.)

Alternatively we could make sure that files in /etc/jed_init.d do the
appropriate checks with e.g.
   search_path_for_file()                        for single files and
   is_substr("my_dir", "get_jed_library_path")   for directories

(I do not remember the actual problem, so my examples migh be misleading.)

Günter

-- 
G.Milde web.de