Re: [Tack-devel] ACK_HOME and em_path
Moved to https://github.com/davidgiven/ack
Brought to you by:
dtrg
From: <u-...@ae...> - 2019-03-07 16:42:30
|
On Thu, Mar 07, 2019 at 04:02:58PM +0100, David Given wrote: > Filesystem layouts are pretty standard, actually, so precompiled binaries > will be built to use /usr/{share,lib} or /usr/local/{share,lib} depending > on whether the binaries are supplied by the distribution or third-party. > (Or {share,libexec} for the BSDs. 1. Isn't it just the compiler driver program which needs a specific setup? It seems even respect environment vars like ACKDIR (looking at ack-5.5). 2. It is totally straightforward to keep all the stuff in a single file tree and let people put the tree where they like. Who is thought to be the consumer of precompiled binaries? Setting an environment variable is not a big challenge for an aspiring C developer, or is it? This would drop the requirement for the recipient to be a superuser (superuser can as well set up an environment variable, even for all the users, or put a two-line bourne shell wrapper into the PATH in use on the machine). What needs fixing? Rune |