From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <AANLkTim4kgUVBziJybonxWosfd7AdTrq9PgPtDVg-K8u@mail.gmail.com>
References: <AANLkTim4kgUVBziJybonxWosfd7AdTrq9PgPtDVg-K8u@mail.gmail.com>
Date: Sat, 22 Jan 2011 11:20:04 -0500
Message-ID: <AANLkTingK8n_Pf4tT+gvfK7QXSOqA_RfNWppe=Zo7RAo@mail.gmail.com>
From: "Devon H. O'Dell" <devon.odell@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [9fans] maintaining p9p
Topicbox-Message-UUID: a019c5ec-ead6-11e9-9d60-3106f5b1d025

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