Re: BUG REPORT tin 1.9.6 release 20101126 ("Burnside") [UNIX]

Urs Janßen <[email protected]> Tue, 9 Aug 2011 12:04:57 +0200
Newsgroups gmane.network.tin.devel
Message-ID <[email protected]>
On Mon, Aug 08, 2011 at 05:39:06PM +0200, Urs Janßen wrote:
> > Yes, the behavior follows the documentation, but what I mean
> > is why --with-defaults-dir defaults to /etc/tin and not to
> > $sysconfdir/etc/tin? I don't see any reason to install the
> 
> that would default to /usr/local/etc/etc/tin

and even if --with-defaults-dir would expand to $sysconfdir"/tin"
that would be a big change as that expands to
/usr/local/etc/tin when no --prefix or --sysconfdir is given and that is a
totally different location as it were in the past, so the change is not
backward compatible.

we might change that someday, but as tin 2.0 will be released within the
next few weeks and this is a "big" chnage this won't happen in the near
future.

> installation is done to
> 
> 	$(DESTDIR)$(INS_SYSDEF_DIR)
> 
> choosen by --with-install-prefix (=DESTDIR) (defaults to /)
> and --with-defaults-dir= (INS_SYSDEF_DIR) (defaults to /etc/tin/)
> so the full default is /etc/tin/
> 
> but you are right there is a bug in configure.in as it sets
> TIN_DEFAULTS_DIR (the place which is used for reading the defaults file)
> just to INS_SYSDEF_DIR, not to DESTDIR/INS_SYSDEF_DIR, but uses
> $(DESTDIR)$(INS_SYSDEF_DIR) for initiall installation. that's a bug

after discussing this with Thomas Dickey who introduced that special
switch (--with-install-prefix), he said that the current bahavior is as
expected ($DESTDIR) just prefixes the installation is not ment to be
evaluated by the resulting binary. this is used to installations into path
where it should not be executed but used as binaries source for building
packages (which lateron do not go into $DESTDIR prefixed locations).

urs
-- 
"Only whimps use tape backup: _real_ men just upload their important stuff
 on ftp, and let the rest of the world mirror it ;)" - Linus