From: "Devon H. O'Dell" <devon.odell@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] maintaining p9p
Date: Sat, 22 Jan 2011 11:20:04 -0500 [thread overview]
Message-ID: <AANLkTingK8n_Pf4tT+gvfK7QXSOqA_RfNWppe=Zo7RAo@mail.gmail.com> (raw)
In-Reply-To: <AANLkTim4kgUVBziJybonxWosfd7AdTrq9PgPtDVg-K8u@mail.gmail.com>
2011/1/22 Rudolf Sykora <rudolf.sykora@gmail.com>:
> Hello,
>
> seems I really don't understand much presently.
>
> The p9p install(1) says:
> ----
> Once the system is built for the first time, it can be maintained and
> rebuilt using mk(1). To rebuild individual commands or libraries, run
> mk install and mk clean in the appropriate source directory (see
> src(1)).
> ----
>
> I use hg. So from time to time I do 'hg pull -u'. Now, it seems to be
> always safe to run ./INSTALL from the top directory. This, however,
> seems to build everything over again, probably unnecessarily. I
> thought I'd call sth like 'mk install' from the top directory to build
> only new/changed stuff. However there is no mkfile there. How should I
> understand the cited?
I think the implication it is making is essentially that *you* need to
know what you want to rebuild. (Also worth noting that a full rebuild
is usually quite fast.)
Hope that clarifies things,
--dho
> Thanks!
> Ruda
>
>
next prev parent reply other threads:[~2011-01-22 16:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-22 16:10 Rudolf Sykora
2011-01-22 16:20 ` Devon H. O'Dell [this message]
2011-01-22 16:26 ` Bakul Shah
2011-01-22 17:07 ` Jacob Todd
2011-01-22 18:03 ` Rudolf Sykora
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='AANLkTingK8n_Pf4tT+gvfK7QXSOqA_RfNWppe=Zo7RAo@mail.gmail.com' \
--to=devon.odell@gmail.com \
--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).