FreeTDS Development Group

[Steve Langasek <vorlon AT netexpress.net>]

On Thu, Jun 13, 2002 at 08:28:55AM -0500, Mark H. Wood wrote:
> On Thu, 13 Jun 2002, Brian Bruns wrote:
> [snippage]
> > > IOW, no /usr/local/etc, per FHS at any rate.  I say
> > >
> > > ./configure --with-prefix=/usr/local --sysconfdir=/etc/freetds
> > >
> > > looks like a winner.  What do you say?

> > I'm in agreement if everyone else is.  My main concern is that we do this
> > change once and only once.

> Hmmm, shouldn't that be '--sysconfdir=/etc'?  Then, if the kit wants to
> put configuration stuff in a 'freetds' subdirectory, it should refer to it
> as $SYSCONFDIR/freetds.  No?

> (You see, I got tired of playing hunt-the-config long ago and coded an
> /etc/config.site:

> # Site defaults for GNU autoconf

> test "$localstatedir" = '${prefix}/var' && localstatedir=/var
> test "$sysconfdir" = '${prefix}/etc' && sysconfdir=/etc

> so no matter what the kit thinks SYSCONFDIR ought to be, it makes no
> difference here.

> I also have a number of symlinks back from hither/etc, yon/etc, usw. to
> /etc to support stuff that was compiled before I concocted my
> config.site.)

The issue is that there are two different layouts commonly used:

/usr/local/etc
          /lib
          /bin
          /sbin,

or

/usr/local/package/etc
                  /lib
                  /bin
                  /sbin.

So if you write your code to use $sysconfdir/freetds/<file>, with the
latter layout you would be looking in /usr/local/freetds/etc/freetds/,
which is redundant and ugly.  Then again, my personal feeling is that
creating separate heirarchies for each site-installed package is *also*
redundant and ugly, so maybe it shouldn't be supported at all. ;)

Steve Langasek
postmodern programmer

Attachment: pgpJ90pcZRVZU.pgp
Description: PGP signature