9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Patrick Kelly <kameo76890@gmail.com>
To: "weigelt@metux.de" <weigelt@metux.de>,
	Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Binary format
Date: Thu, 18 Feb 2010 10:08:19 -0500	[thread overview]
Message-ID: <7C16E1A2-9617-42AB-AFA5-11AC7805DAA1@gmail.com> (raw)
In-Reply-To: <20100217150452.GE10816@nibiru.local>



On Feb 17, 2010, at 10:04 AM, Enrico Weigelt <weigelt@metux.de> wrote:

> * Steve Simon <steve@quintile.net> wrote:
>
>> 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
>
> A possible solution could be an package management system which
> knows dependencies and so can tell what to rebuild.

Entia non sunt multiplicanda praeter necessitatem
>
>> It also neatly sidesteps the issue that different applications
>> can need different versions of a single shared library. This
>> is a real problem on some OSs (see 9fans passim).
>
> Actually, that's just a matter of clean dependency handling.
> Include an API/ABI version in the filename, etc.
>
>
> cu
> --
> ----------------------------------------------------------------------
> Enrico Weigelt, metux IT service -- http://www.metux.de/
>
> phone:  +49 36207 519931  email: weigelt@metux.de
> mobile: +49 174 7066481   icq:   210169427         skype: nekrad666
> ----------------------------------------------------------------------
> Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
> ----------------------------------------------------------------------
>



  parent reply	other threads:[~2010-02-18 15:08 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
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 [this message]
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=7C16E1A2-9617-42AB-AFA5-11AC7805DAA1@gmail.com \
    --to=kameo76890@gmail.com \
    --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).