From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] qt4.inc: remove the optional documentation package from the demo's RRECOMMENDS
Date: Mon, 5 Sep 2011 16:51:01 +0100 [thread overview]
Message-ID: <201109051651.01532.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <FA68554D-DEC9-44B3-8971-AA7F01B068A8@dominion.thruhere.net>
On Monday 05 September 2011 16:38:42 Koen Kooi wrote:
> Op 5 sep. 2011 om 15:24 heeft Denis Carikli <denis@eukrea.com> het volgende
geschreven:
> > The documentation is 285M and doesn't fit on the NAND of many machines.
>
> That does remove all the descriptions from the qtdemo app, so removing all
> docs isn't a good idea
This is what I was afraid of when the discussion came up on IRC. The proper
solution is to split out the files required for the descriptions to a separate
package. I don't know which files those are however.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-09-05 15:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 13:24 [PATCH] qt4.inc: remove the optional documentation package from the demo's RRECOMMENDS Denis Carikli
2011-09-05 15:38 ` Koen Kooi
2011-09-05 15:47 ` Eric Bénard
2011-09-05 15:51 ` Paul Eggleton [this message]
2011-09-05 16:04 ` Eric Bénard
2011-09-05 21:13 ` Eric Bénard
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=201109051651.01532.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--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 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.