From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <264bf83cedae0aa71f136a878b2d88e7@bellsouth.net>
To: weigelt@metux.de, 9fans@9fans.net
Date: Wed, 17 Feb 2010 09:48:01 -0600
From: blstuart@bellsouth.net
In-Reply-To: <20100217150452.GE10816@nibiru.local>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Binary format
Topicbox-Message-UUID: d4f51498-ead5-11e9-9d60-3106f5b1d025

>> We recompile the relevant executables. The speed of kencc makes this
>> much less painful than you might expect. It also happens very rarely
>> on plan9 - I cannot remember the last time we had a "big" pull.
>
> Okay, but then (as an admin) you have to know which apps have
> to be recompiled. For a small system this might be okay, but
> that doesnt scale well ;-o

Keep in mind that Plan 9 isn't a new OS just waiting for thousands
of GNU apps to be ported.  Plan 9 is over 20 years old and has
a community that's developed native apps and a few selected
ports for the things the community finds useful.  So the kind of
apps explosion that would require it to scale well is anathama to
the culture.  Certainly there are things that would be welcomed
to be be written, and a few even ported.  But having 72 different
X11 widget "toolboxes" and 42 different GUI versions of diff
will meet with a resounding thud.  Eye candy, complexity, and
mainstream popularity don't impress the people in the Plan 9
community; elegance and originality do.

But beyond that, the main distribution includes both binaries
and source for updates.  So a pull will generally get everything
you need without needing to recompile.  And if you do want to
recompile everything, running mk in /sys/src will recompile
everything and not take all that long doing it, especially if you
keep the object files around.

BLS