From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Raspberry Pi: keyboard layout
Date: Mon, 3 Dec 2012 21:41:17 -0500 [thread overview]
Message-ID: <35632e84336e8eae2e5d0e306f10c3f8@brasstown.quanstro.net> (raw)
In-Reply-To: <20121204015250.0FC02B827@mail.bitblocks.com>
> 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.
sure, that works. i'd almost rather have an install script
that does the building for you. but for now i've updated
all my contrib packages to include 386/amd64/arm.
- erik
next prev parent reply other threads:[~2012-12-04 2:41 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
2012-12-04 2:41 ` erik quanstrom [this message]
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=35632e84336e8eae2e5d0e306f10c3f8@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--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).