From: Alexis <surryhill@gmail.com>
To: Ingo Schwarze <schwarze@usta.de>
Cc: Kristaps Dzonsons <kristaps@bsd.lv>, tech@mdocml.bsd.lv
Subject: Re: Allow configure variables to be set from environment
Date: Thu, 22 Jan 2015 08:26:25 +0100 [thread overview]
Message-ID: <20150122072625.GA1198@kei> (raw)
In-Reply-To: <20150121230518.GF11796@iris.usta.de>
Hi Ingo,
thanks for the changes!
I'll test as soon as Kristaps patch has made it into CVS.
In Hombrew what you named HOMEBREWDIR is named HOMEBREW_PREFIX,
it may or may not make sense to name the two alike.
Additionally I'd set the default of HOMEBREWDIR in
configure.local.example to either /usr/local (which is the default
installation directory of Homebrew as suggested on http://brew.sh) or
/opt/homebrew, but not /Cellar. There is a Cellar sub-directory in the
Homebrew tree where all the installed software (they call them kegs)
reside and it might be confusing people.
It just occurred to me that you actually mean Cellar and want mandoc
to only use the files from the Cellar (due to the symlinks mentioned
in previous messages) in which case I'd rename HOMEBREWDIR to
HOMEBREW_CELLAR set its default to /usr/local/Cellar to make it more clear.
Best,
Alexis
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2015-01-22 7:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <sfid-H20150116-225859-+021.89-1@spamfilter.osbf.lua>
2015-01-16 21:58 ` Alexis
2015-01-16 23:32 ` Thomas Klausner
2015-01-17 1:31 ` Ingo Schwarze
2015-01-17 1:07 ` Ingo Schwarze
2015-01-17 20:10 ` Kristaps Dzonsons
2015-01-18 3:33 ` Ingo Schwarze
2015-01-20 15:15 ` Alexis
2015-01-21 23:05 ` Ingo Schwarze
2015-01-22 0:21 ` Kristaps Dzonsons
2015-01-22 0:35 ` Ingo Schwarze
2015-01-22 7:32 ` Alexis
2015-01-22 7:26 ` Alexis [this message]
2015-01-23 22:05 ` Ingo Schwarze
2015-01-20 15:19 ` Alexis
2015-01-21 21:07 ` Ingo Schwarze
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=20150122072625.GA1198@kei \
--to=surryhill@gmail.com \
--cc=kristaps@bsd.lv \
--cc=schwarze@usta.de \
--cc=tech@mdocml.bsd.lv \
/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;
as well as URLs for NNTP newsgroup(s).