i've just started playing with it.  why are the binaries installed in
/n/other/kirara?

on fossil i had to fake /n/other/kirara with:

aux/stub -d /n/other/kirara
mkdir kirara && chmod +t kirara
bind -c /n/other/kirara kirara
mk install

but it doesn't install correctly:

% kirara=`{pwd}^/kirara
% kfind snoop
Can't cd /n/other/kirara/sysdb: '/n/other/kirara' does not exist
grep: can't open Dir: 'Dir' file does not exist
Can't cd /n/other/kirara/usrdb: '/n/other/kirara' does not exist
grep: can't open Dir: 'Dir' file does not exist
%



On Tue, Aug 6, 2013 at 11:31 PM, arisawa <arisawa@ar.aichi-u.ac.jp> wrote:

> Hello 9fans,
>
> Thanks for the attention to Kirara.
> There was bugs in document, and probably in programs.
> These bug reports are helpful for me.
> There is room for improvement, any comment is welcome for future
> development.
>
> Kenji Arisawa
>
> On 2013/08/07, at 3:14, brz-systemd-dev@intma.in wrote:
>
> > I've played around with Kirara for a couple hours, now, and am pretty
> > surprised at how simple it is.  It's already become integrated into my
> > workflow.  Being able to quickly (and easily) search for relevant
> > snippets of code throughout the system is quite useful.
> >
> > I feel compelled to mention that the code is abnormally high in
> > quality.  (This is seen, even in the rc scripts)
> > Now I'm going to have to look through your other projects.
> >
> > Thanks for releasing this.
> >
> > - BurnZeZ
> >
> > Bug:
> >       kirara-1.1/INSTALL:9: mkdir -p $kirarar/bin/^(rc $objtype)
> >       Here (and on line 11), '$kirarar' is used instead of '$kirara'.
> >
>
>
>
>