>
> In article <199908100226.WAA18044@astro.fccj.cc.fl.us> you wrote:
>>
>> I have a small nit; when I say -
>>
>> ./configure --prefix=.
>>
>> I would like the configure script to know I meant -
>>
>> ./configure --prefix=`pwd`
>
> Hmmm.... a little bit strange feature request, I think. I'm not sure of the
> usefulness of this, because --prefix=`pwd` is more for developers than for end
> users and developers should not need such convinience mappings. At least
> --prefix options are never intended to have relative paths. So I would more
> vote to add another test which makes sure the argument of --prefix starts with
> a slash.
> Ralf S. Engelschall
> rse@engelschall.com
> www.engelschall.com
>
I agree. End-users would possibly not know about . vs `pwd`,
but using . when you meant `pwd` breaks the run-time.
-Sneex- :]
|