9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: arisawa <arisawa@ar.aichi-u.ac.jp>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] text database Kirara
Date: Wed,  7 Aug 2013 17:17:23 +0900	[thread overview]
Message-ID: <C8ACAFB4-EE8B-442B-9644-40320E780ED8@ar.aichi-u.ac.jp> (raw)
In-Reply-To: <CAJSxfm+z3y12FJnjbad5uKZ=CLGOX2haO4vr5SN_LWcjLyA-TA@mail.gmail.com>

Hello Skip,

On fossil, Kirara can be installed anywhere.
Let the directory be $kirara.
It is desirable that the directory is out of Kirara's target,
and out of fs dump.
On fossil, execute
	chmod +t $kirara
You must set the environment variable, otherwise you must
change all /n/other/kirara in the scripts to the place.

To install Kirara, change the line in mkfile
	kirara=/n/other/kirara
to the directory. ( sorry I forgot to instruct this one)

Kirara's binary is installed to $kirara/bin. Because Kirara introduced many new tools
that might conflict existing binaries. Therefore it is safe not to mix with your binaries.

Kenji Arisawa

On 2013/08/07, at 16:22, Skip Tavakkolian <skip.tavakkolian@gmail.com> wrote:

> 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'.
> >
> 
> 
> 
> 




  reply	other threads:[~2013-08-07  8:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-06  1:14 arisawa
2013-08-06  7:26 ` Francisco J Ballesteros
2013-08-06  8:12 ` Peter A. Cejchan
2013-08-06 18:14 ` brz-systemd-dev
2013-08-07  6:31   ` arisawa
2013-08-07  7:22     ` Skip Tavakkolian
2013-08-07  8:17       ` arisawa [this message]
2013-08-07 13:32         ` erik quanstrom

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C8ACAFB4-EE8B-442B-9644-40320E780ED8@ar.aichi-u.ac.jp \
    --to=arisawa@ar.aichi-u.ac.jp \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).