From: Mike Westerhof <mike@mwester.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: xterm: either fix it, or remove it. please.
Date: Thu, 12 Nov 2009 12:49:20 -0600 [thread overview]
Message-ID: <4AFC58B0.3080000@mwester.net> (raw)
In-Reply-To: <ac9c93b10911120447k496f094bg478dc05ae612b4a9@mail.gmail.com>
Frans Meulenbroeks wrote:
> So it is not really fedora specific, but it is SELinux specific.
> Do we want to support SELinux as build host ?
Do we want to? Yes, it would be a nice thing to support.
Is it practical? I think the answer is no. In my experience, tools
like selinux have a tendency to require inordinate amounts of
administrative burden that just isn't practical in a development
environment. I think requiring that selinux be disabled on build hosts
is a reasonable requirement, and will avoid wasting a lot of cycles that
should be spent on OE, and not on administration (or sending lots of
emails).
-Mike (mwester)
next prev parent reply other threads:[~2009-11-12 18:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 5:47 xterm: either fix it, or remove it. please Robert P. J. Day
2009-11-12 5:56 ` Holger Hans Peter Freyther
2009-11-12 6:22 ` Robert P. J. Day
2009-11-12 6:22 ` Holger Hans Peter Freyther
2009-11-12 6:36 ` Robert P. J. Day
2009-11-12 7:20 ` Holger Hans Peter Freyther
2009-11-12 7:32 ` Holger Hans Peter Freyther
2009-11-12 7:34 ` Robert P. J. Day
2009-11-12 8:33 ` Michael 'Mickey' Lauer
2009-11-12 8:28 ` Graeme Gregory
2009-11-12 8:15 ` Frans Meulenbroeks
2009-11-12 12:28 ` Robert P. J. Day
2009-11-12 12:47 ` Frans Meulenbroeks
2009-11-12 12:58 ` Robert P. J. Day
2009-11-12 13:05 ` Graeme Gregory
2009-11-12 15:37 ` Robert P. J. Day
2009-11-12 13:11 ` Holger Hans Peter Freyther
2009-11-13 8:43 ` Robert P. J. Day
2009-11-13 8:55 ` Robert P. J. Day
2009-11-13 9:32 ` Graeme Gregory
2009-11-12 13:15 ` Robert P. J. Day
2009-11-12 18:49 ` Mike Westerhof [this message]
2009-11-12 21:42 ` GNUtoo
2009-11-12 21:59 ` Philip Balister
2009-11-12 22:17 ` Graeme Gregory
2009-11-13 4:38 ` Robert P. J. Day
2009-11-12 11:51 ` Philip Balister
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=4AFC58B0.3080000@mwester.net \
--to=mike@mwester.net \
--cc=openembedded-devel@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.