bug 219448

[G. Milde]

On 12.05.05, Paul Boekholt wrote:
> 
> On Thu, 12 May 2005 09:19:56 +0200, "G. Milde" <g.milde@web.de> said:
> > On 11.05.05, Jörg Sommer wrote:
> > > G. Milde schrieb am Wed 11. May, 14:09 (+0200):
> 
> > > > This raises the more generic question: should a locally installed program
> > > > read configuration files in /etc/ (which might belong to non-local
> > > > programs or be just leftovers)?
> 
> > > I think, no.

> I don't know, it seems most local programs do look for conffiles it /etc,
> regardless of how they were built.

Well, what shall we do?

  * stick with the others and search /etc/ as well as /usr/local/etc/ in any
    case?
    
    Even if the old Debian-specific files in /etc/ where annoying for Paul, 
    the behaviour is at least "expectable" when mixing a package with a
    local instllation. My workaroud suggestion would be an (empty)
    defaults.sl in /usr/local/jed/lib/. This would stop the search for
    jed.conf in the current version.
    
  * use the simpler (and Paul-friendly) approach with only /etc/ or local
    search?
    
  * Ask jed-users?
  
Günter    


-- 
G.Milde web.de