Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] tzdata: install /etc/localtime alongside /etc/timezone
Date: Fri, 31 Aug 2012 15:29:41 +0100	[thread overview]
Message-ID: <1346423384.2673.102.camel@phil-desktop> (raw)
In-Reply-To: <1346278937.4396.57.camel@x121e.pbcl.net>

On Wed, 2012-08-29 at 23:22 +0100, Phil Blundell wrote:
> As far as I know, only Intel have ever expressed any real interest in
> having this feature work.  My recollection is that there are some
> supposed "carrier grade" systems where this is, for whatever reason, a
> requirement. 

None of the carrier-grade people (or indeed any others) seem to have
spoken up in favour of a separate /usr in the past 3 days or so, which
does rather suggest that nobody actually cares about it.  

Maybe the TSC would like to reconsider whether this is in fact a
worthwhile thing to go on trying to support in oe-core or whether it
should just assume that / and ${prefix} will be the same filesystem.

p.





  parent reply	other threads:[~2012-08-31 14:41 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-29 14:24 [PATCH 0/2] tzdata fixes Ross Burton
2012-08-29 14:24 ` [PATCH 1/2] tzdata: this package isn't architecture specific Ross Burton
2012-08-29 14:24 ` [PATCH 2/2] tzdata: install /etc/localtime alongside /etc/timezone Ross Burton
2012-08-29 14:47   ` Koen Kooi
2012-08-29 14:49     ` Paul Eggleton
2012-08-29 15:23     ` Burton, Ross
2012-08-29 16:50       ` Koen Kooi
2012-08-29 16:57         ` Burton, Ross
2012-08-29 17:01           ` Paul Eggleton
2012-08-29 17:31             ` Burton, Ross
2012-08-29 19:12               ` Phil Blundell
2012-08-29 19:20                 ` Burton, Ross
2012-08-29 21:38                   ` Khem Raj
2012-08-29 21:50                     ` Burton, Ross
2012-08-29 22:22                       ` Phil Blundell
2012-08-29 22:45                         ` Khem Raj
2012-08-30 10:00                         ` Burton, Ross
2012-08-30 10:21                           ` Phil Blundell
2012-08-31 14:29                         ` Phil Blundell [this message]
2012-08-31 14:34                           ` Khem Raj
2012-08-31 16:01                           ` Richard Purdie
2012-08-31 16:45                             ` Khem Raj
2012-08-31 21:31                               ` Khem Raj
2012-09-01 17:30                                 ` Andrea Adami
2012-09-04 16:28                                   ` Mark Hatle
2012-09-04 19:26                                     ` Burton, Ross
2012-09-04 19:44                                       ` Mark Hatle
2012-09-04 20:06                                         ` Burton, Ross
2012-09-04 20:40                                           ` Mark Hatle
2012-09-04 21:29                                     ` Khem Raj
2012-09-06  9:32                                       ` Paul Eggleton
2012-09-07 16:30                                         ` Khem Raj
2012-09-04 16:16                             ` Mark Hatle
2012-08-30  9:48         ` Burton, Ross
2012-08-29 14:45 ` [PATCH 0/2] tzdata fixes Koen Kooi

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=1346423384.2673.102.camel@phil-desktop \
    --to=philb@gnu.org \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox