Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: csmall@eye-net.com.au (Craig Small)
To: pa3gcu <pa3gcu@zeelandnet.nl>
Cc: w9ya <w9ya@amsat.org>, Hamish Moffatt <hamish@cloud.net.au>,
	linux-hams@vger.kernel.org
Subject: Re: ax25ipd
Date: Thu, 29 Aug 2002 21:19:09 +1000	[thread overview]
Message-ID: <20020829111909.GG13358@eye-net.com.au> (raw)
In-Reply-To: <0208280548330G.02211@unix.pa3gcu>

On Wed, Aug 28, 2002 at 05:48:33AM +0000, pa3gcu wrote:
> Looks like i started this thread, what i mean was, why do the ax25lib/apps/ 
> and tools default to /usr/local and place binarys in /usr/local when some 
> programs will "still" look in /etc/ax25 for thier config files instead of 
> /usr/local/etc thats what i mean, seems like a funny way of doing things to 
> me.
Because people build the programs inconsistently.  More specifically
they build the libraries with one set of options and the binaries with
another.

> Yes the program concernd has the -C option, yes there is the 
> ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var
> But folks dont read documentation do they and we constanly see this question 
> poping up here on this list simply because one did not read the docs 
> beforehand.
Well, the must be reading it once then forgetting it.  If they do the
same thing then there is no problem.

The ax25 stuff uses standard auto* tools folks, its pretty common out
there and probably the most common sort of build set.

People don't read documentation, I get plenty of emails that are FAQs;
not just in ax25 stuff.

Part of the problem has been dumb error messages that don't say where
they are looking.  I believe that is being fixed now.

  - Craig
-- 
Craig Small VK2XLZ  GnuPG:1C1B D893 1418 2AF4 45EE  95CB C76C E5AC 12CA DFA5
Eye-Net Consulting http://www.eye-net.com.au/        <csmall@eye-net.com.au>
MIEEE <csmall@ieee.org>                 Debian developer <csmall@debian.org>

      parent reply	other threads:[~2002-08-29 11:19 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-26  2:25 ax25ipd N1UAN Bob
2002-08-26  4:29 ` ax25ipd Steve Fraser
2002-08-26  3:13   ` ax25ipd N1UAN Bob
2002-08-26  6:17     ` ax25ipd pa3gcu
2002-08-26  7:43       ` ax25 Michael Hart
2002-08-26 13:12         ` ax25 pa3gcu
2002-08-26 15:46           ` ax25 M Taylor
2002-09-22 11:07         ` ax25 Michael Hart
2002-09-22 12:21           ` ax25 pa3gcu
2002-09-22 14:10             ` ax25 Michael Hart
2002-09-22 15:37               ` ax25 Tomi Manninen
2002-09-22 17:54                 ` ax25 M Taylor
2002-09-29  0:43                   ` ax25 Michael Hart
2002-09-29  1:54                     ` ax25 Bob Nielsen
2002-08-26 20:08 ` ax25ipd Andrew B.
2002-08-26 20:53   ` ax25ipd pa3gcu
2002-08-26 21:47     ` ax25ipd w9ya
2002-08-27 12:05       ` ax25ipd Hamish Moffatt
2002-08-27  9:50         ` ax25ipd w9ya
2002-08-27 22:36           ` ax25ipd Hamish Moffatt
2002-08-27 18:22             ` ax25ipd w9ya
2002-08-28  5:48               ` ax25ipd pa3gcu
2002-08-28 10:42                 ` ax25ipd Hamish Moffatt
2002-08-28  8:29                   ` ax25ipd w9ya
2002-08-29 11:19                 ` Craig Small [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020829111909.GG13358@eye-net.com.au \
    --to=csmall@eye-net.com.au \
    --cc=hamish@cloud.net.au \
    --cc=linux-hams@vger.kernel.org \
    --cc=pa3gcu@zeelandnet.nl \
    --cc=w9ya@amsat.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox