On Thu, Sep 27, 2012 at 4:54 PM, Irek Szczesniak <iszczesn...@gmail.com> wrote: > On Thu, Sep 27, 2012 at 4:50 PM, Irek Szczesniak <iszczesn...@gmail.com> > wrote: >> On Thu, Sep 27, 2012 at 3:09 PM, Cedric Blancher >> <cedric.blanc...@googlemail.com> wrote: >>> On 27 September 2012 12:50, ольга крыжановская >>> <olga.kryzhanov...@gmail.com> wrote: >>>> I would like to collect opinions: >>>> For those who desperately wish to have grep, od, tr, xargs in libcmd: >>>> Would it be acceptable to bind these built ins to /opt/ast/bin/grep, >>>> /opt/ast/bin/od, /opt/ast/bin/tr and /opt/ast/bin/xargs? /opt/ast/bin >>>> is a special path (controlled at build time via the SH_CMDLIB_DIR cpp >>>> variable; Solaris uses /usr/ast/bin instead) which can enable built >>>> ins even if they are not present as files in the file system. >>> >>> Yes, this would be acceptable. >> >> Yes, this would work for us as well. > > On a 2nd thought... is there an API to obtain the value of > SH_CMDLIB_DIR? Technically it's not mandatory - if these four are > bound to the path in SH_CMDLIB_DIR then using builtin $name will work, > too.
And on a 3rd thought: You're asking whether I like to see grep, od, tr and xargs in libcmd and bound to the virtual path defined per SH_CMDLIB_DIR, so that if SH_CMDLIB_DIR==/opt/ast/bin then PATH=/opt/ast/bin:$PATH will enable then, right? That would be perfect. Irek _______________________________________________ ast-developers mailing list ast-developers@research.att.com https://mailman.research.att.com/mailman/listinfo/ast-developers
