From: "Eric Bénard" <eric@eukrea.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] qt4.inc: remove the optional documentation package from the demo's RRECOMMENDS
Date: Mon, 05 Sep 2011 23:13:45 +0200 [thread overview]
Message-ID: <4E653B89.2030808@eukrea.com> (raw)
In-Reply-To: <4E64F321.5010008@eukrea.com>
Le 05/09/2011 18:04, Eric Bénard a écrit :
> Le 05/09/2011 17:38, Koen Kooi a écrit :
>> 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
>>
> yes, that brings oe-core to the oe dev state (where the docs were not installed).
> This makes qt4-demo images usable on systems with 256 MB flash because the doc
> package is huge.
>
FWIW with this patch we have exactly the same behaviour as (for example) a
Fedora 15 : installing qt-demos brings a qt-demo program which can launch the
demos and examples but lacks the explanation text, installing qt-docs brings
the text (in a 126MB rpm !).
> Next step will be to split the doc package in order to have the descriptions
> in one package and the code in an other one. We will try to find time to do
> this in a few days.
>
in fact the text comes from the html directory in the qt doc which is quite
big : 184MB. After a few research, it seems "only" 36MB of these 184MB are
used by qtdemo, so we could quite easily split qt-doc in 2 packages :
qt-demo-doc and qt-doc.
Eric
prev parent reply other threads:[~2011-09-05 21:18 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
2011-09-05 16:04 ` Eric Bénard
2011-09-05 21:13 ` Eric Bénard [this message]
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=4E653B89.2030808@eukrea.com \
--to=eric@eukrea.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox