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

[G. Milde]

On 18.04.05, Jörg Sommer wrote:
> G. Milde schrieb am Mon 18. Apr, 09:50 (+0200) :

> > > 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.
> 
> But jed will never buildable if a version lower than this is installed.
> Think of the jump from sarge to etch. From this point of view our package
> will never buildable and I don't know if this is a policy violation.

I suppose this is tolerable, as long as the packages are in experimental (if
we do properly document it like: "uninstall jed-extra<=nn before updating").

I wonder, whether a pre-install script could do some manipulation or testing, 
though.

 
> > * 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.
> 
> This is ugly.

Agreed. But I wonder whether it would be less ugly to have a Debian
specific patch in site.sl?


> > > 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?
> Yes.
> > AFAIK, these two were never used by Debian, so a Debian package doesnot
> > need to take care of them explicitely.
> 
> No. I see the bugreport coming: "If I have a local jed.conf in
> /usr/local/etc/jed.conf (which is FHS conform) I can not build jed."

This very much depends on what is in this file. If I remember
right, the problem arose from code in /etc/jed_init.d evaluated by
jed.conf. I doubt, a user or admin will replicate the jed_init.d
screening in a local jed.conf.
 
> We can't hobble debian users and admins with such assumtions.

OTOH, we can't safeguard against all possible local extensions.


> > 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
> 
> This prevents overlaying files and package versions by a local version by
> placing them before the real version in jed_library_path.

I do not want to add paths or create directories but just check if a file
or directory exists before acting on it (or trying to byte-compile a file
in it).

Finally, we could also try an ERROR_BLOCK to keep jed running, but I am
not sure whether it will help in this particular case.

Günter

BTW: is there an archive of this list?

-- 
G.Milde web.de