[avahi] Installation on SuSE 10.0

[Lennart Poettering]

On Mon, 20.02.06 21:05, Peter Onion (Peter.Onion at btinternet.com) wrote:

> 
> On Mon, 2006-02-20 at 20:17 +0100, Lennart Poettering wrote:
> > On Mon, 20.02.06 18:17, Peter Onion (Peter.Onion at btinternet.com) wrote:
> > 
> > > 
> > > On Mon, 2006-02-20 at 00:45 +0100, Sebastien Estienne wrote:
> > > 
> > > > you could use "--sysconfdir=/etc --localstatedir=/var"
> > > > 
> > > > so you won't need to copy initscripts and you'll have your avahi
> > > > config files in /etc/
> > > > and no need for the "mkdir -p /usr/local/var/run/"
> > > 
> > > If these are the "correct" paths, then could they be made the default
> > > values so that new users don't make the same mistake I made ? 
> > 
> > Because all autoconf apps work that way. 
> 
> But all other autoconfs work !

Only if they don't install files in $(localstatedir) or
$(sysconfdir). Only a minority does that, one of them being avahi. All
autoconf apps that use $(localstatedir) are probably "broken" in your
eyes then.

> > To deviate from the known behaviour might confuse even more people. 
> 
> Having to provide non-default options mightconfiuse people too!

Sure, but that's a common issue with autoconf apps, so people should
already know. And if they don't they learned something for
life... ;-)

> I think every other autoconf application I've installed either gets the
> paths right by default without having to provide anything on the
> configure command line or produces a working installation with the
> defaults.   IMHO the avahi autoconf is borked if it can produce none
> working installations !

Yes, I admit it would make sense to create $(localstatedir) on "make
install". In your setup however, this would lie in /usr/local/var/,
which might be not what you want.

Lennart

-- 
Lennart Poettering; lennart [at] poettering [dot] net
ICQ# 11060553; GPG 0x1A015CC4; http://0pointer.net/lennart/