9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Raspberry Pi: keyboard layout
Date: Mon,  3 Dec 2012 17:52:50 -0800	[thread overview]
Message-ID: <20121204015250.0FC02B827@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Mon, 03 Dec 2012 13:38:09 CST." <8CD17BB7-A598-47EF-833B-702F0CDC5306@gmail.com>

On Mon, 03 Dec 2012 13:38:09 CST Chris Wilson <christopher.j.wilson@gmail.com>  wrote:
> On Dec 3, 2012, at 11:00 AM, Richard Miller wrote:
>
> >> Do you have
> >> some sort of site where I would be able to find out when you upload new
> >> images?
> >
> > Nothing formal - you can check the modified date of the image file in
> > /n/sources/contrib/miller to see if it's changed.  The official install
> > and update mechanism for Plan 9 at present is a bit x86 dependent.
> > Eventually I hope arm systems in general will become more integrated.
>
> If there is anything that myself, fairly noobish that I am, can do to help,
> let me know. Great work on the Pi image! I've been loving it.

Not sure this is for newbies but...

contrib/* doesn't distinguish between archs.  One suggestion
is to enhance contrib/*. Probably best for the contrib author
to do this (or provide directions) but I am thinking something
along these lines:

- when installing or pulling changes, build things locally if
  $objtype specific binaries don't exist in the package.  And
  don't pull binaries for other archs (unless explicitly asked
  for).

- when creating or pushing changes, try to push binaries for
  all the archs locallly (cross) compiled.

- when listing don't show packages known to be broken for
  $objtype arch. Probably best to add config/broken and
  config/fixed.



  reply	other threads:[~2012-12-04  1:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-03  0:45 Murray Colpman
2012-12-03  1:08 ` Bakul Shah
2012-12-03  1:33   ` Murray Colpman
2012-12-03  2:10     ` Christopher Wilson
2012-12-03  9:42     ` Richard Miller
2012-12-03 16:44       ` Murray Colpman
2012-12-03 17:00         ` Richard Miller
2012-12-03 19:38           ` Chris Wilson
2012-12-04  1:52             ` Bakul Shah [this message]
2012-12-04  2:41               ` erik quanstrom
2012-12-03 16:23     ` Christian Neukirchen
2012-12-03 16:48       ` Richard Miller
2012-12-04 14:10       ` Christian Neukirchen
2012-12-03  0:57 Erik Quanstrom
2012-12-03  1:05 ` Murray Colpman

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=20121204015250.0FC02B827@mail.bitblocks.com \
    --to=bakul@bitblocks.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).