9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: blstuart@bellsouth.net
To: weigelt@metux.de, 9fans@9fans.net
Subject: Re: [9fans] Binary format
Date: Wed, 17 Feb 2010 09:48:01 -0600	[thread overview]
Message-ID: <264bf83cedae0aa71f136a878b2d88e7@bellsouth.net> (raw)
In-Reply-To: <20100217150452.GE10816@nibiru.local>

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




  parent reply	other threads:[~2010-02-17 15:48 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-17 13:31 Enrico Weigelt
2010-02-17  8:50 ` Jacob Todd
2010-02-17 13:58   ` Enrico Weigelt
2010-02-17 14:01     ` erik quanstrom
2010-02-17 14:06 ` Gorka Guardiola
2010-02-17 14:13   ` David Leimbach
2010-02-17 14:33   ` Enrico Weigelt
2010-02-17 14:55     ` Steve Simon
2010-02-17 15:04       ` Enrico Weigelt
2010-02-17 15:29         ` erik quanstrom
2010-02-17 15:48         ` blstuart [this message]
2010-02-17 17:54           ` lucio
2010-02-17 18:37         ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2010-02-17 19:00         ` Nick LaForge
2010-02-18 15:08         ` Patrick Kelly
2010-02-17 15:58       ` David Leimbach
2010-02-17 16:14       ` Stuart Morrow
2010-02-17 16:28         ` David Leimbach
2010-02-17 18:21           ` Enrico Weigelt
2010-02-17 18:34             ` David Leimbach
2010-02-17 19:02               ` Enrico Weigelt
2010-02-17 19:35                 ` Enrico Weigelt
2010-02-17 18:38             ` Corey Thomasson
2010-02-18 15:16             ` Patrick Kelly
2010-02-17 15:13     ` Robert Raschke
2010-02-17 21:32     ` Jacob Todd
2010-02-17 21:26   ` Nathaniel W Filardo
2010-02-17 23:16     ` EBo
2010-02-17 23:22       ` David Leimbach
2010-02-17 14:38 ` blstuart
2010-02-17 14:58   ` Enrico Weigelt
2010-02-17 15:25     ` blstuart

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=264bf83cedae0aa71f136a878b2d88e7@bellsouth.net \
    --to=blstuart@bellsouth.net \
    --cc=9fans@9fans.net \
    --cc=weigelt@metux.de \
    /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).