Re: GNU GLOBAL - few patches

[Shigio Yamaguchi]

> Now, if some user doesn't have libhome_etc (nor HOME_ETC variable set), he al
so can
> customize globash home directory, using GLOBASH_HOME (_almost_ same way he
> can customize gtags configuration file using GTAGSCONF).

I don't think globash needs such customizing.
I just think that if an environment support some mechanism like home_etc,
GLOBAL should obey it not to be isolated from the rest.

> home-etc compliant scripts which we are sure that are in touch with
> user's environment doesn't have to call some binary (and the library via it),
> they can simply trust the HOME_ETC variable's value.

I understand.

> Of course, it would be nice if the globash.rc contained:
> 
> if [ -n "$GLOBASH_HOME" ]; then
>      GHOME=$GLOBASH_HOME/.globash
> elif [ -n "$HOME_ETC" ]; then
>      GHOME=$HOME_ETC/.globash
> else
>      GHOME=$HOME/.globash
> fi

How about this?

        if [ -n "$HOME_ETC" ]; then
             GHOME=$HOME_ETC/.globash
        else
             GHOME=$HOME/.globash
        fi

The GLOBASH_HOME facility is independent of home_etc facility, I think.

> for empty or 'yes' it should be set to /usr/local
> 
> standard tree for the library is:
> 
> /usr/local
> |
> +-- include (home_etc.h)
> |
> +-- lib (libhome_etc.a libhome_etc.so)
> |

OK. I'll use '/usr/local'.
Thank you.
--
Shigio Yamaguchi <address@hidden> - Tama Communications Corporation
PGP fingerprint: D1CB 0B89 B346 4AB6 5663  C4B6 3CA5 BBB3 57BE DDA3