Johannes Hofmann (2010-01-26 13:55):
On Tue, Jan 26, 2010 at 09:34:17AM -0300, Jorge Arellano Cid wrote:
On Tue, Jan 26, 2010 at 03:42:44AM +0000, corvid wrote:
Jorge wrote:
On Mon, Jan 25, 2010 at 03:55:39AM +0000, corvid wrote:
- Why does install-dpi-local put dpidc in ~/.dillo, anyway? Wouldn't that be unusual for it to be in anyone's path?
The idea was to have most dillo-related things in that directory. Subdirectories in ~/bin look rare, so lacking a better idea it ended in ~/.dillo
To me, it makes the most sense to put it wherever dillo goes.
Yes, I agree. Sorry, I was thinking of the dpis.
The user may not have permission to install system-wide, and in that case probably dillo, dpid, and dpidc should be in ~/bin and the dpis in ~/.dillo/dpi.
Do we really need to add special handling for this? Normally I would expect binaries in $PREFIX/bin and dpis also in $PREFIX/bin or $PREFIX/libexec. The user has to use a PREFIX where he has write access of course. But then the rest is taken care of by autoconf and friends, no?
At most, the instructions to build dillo [1] could include suggestions how to run dillo locally. No more special handling should be needed (autoconf takes care of this case, yes). The instructions could be as scarce as this (hope they are correct): If you choose to install under a different prefix (./configure --prefix=dir), note that dillo needs the binaries dpid, dpidc to be in your $PATH. [1] http://www.dillo.org/source.html P.S. Is everyone comfortable with the colors at dillo.org? The logo is nice, but the light background with white text means sore eyes to me. -- -- Rogut?s Sparnuotos