From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: poky@yoctoproject.org
Subject: Re: gnupg strip down
Date: Tue, 25 Apr 2017 16:10:57 +0300 [thread overview]
Message-ID: <29aeb088-beb1-7fa2-b95a-c534f853b374@linux.intel.com> (raw)
In-Reply-To: <trinity-1c5fd78a-c6ca-41a1-8dea-dcfe8bf1ff35-1493125020120@3capp-gmx-bs23>
On 04/25/2017 03:57 PM, star@gmx.li wrote:
> Would like to include gnupg into my filesystem. If I add gnupg to my image, it become to big (12.5MB instead of 5MB with core-image-minimal).
> It installs a lot of things I don't need: dozen libs, binaries and even helpfiles in all languages ?!?
>
> In fact I need just gnupg-binary and around 5 libs for my need. Can you help me howto strip down the recipe or what has to be set in a bbappend file to achive that? My first experiments with adding things to ETXRA_OECONF like
>
> EXTRA_OECONF = "....
> --disable-card-support \
> --disable-gnupg-iconv \
> --disable-idea \
> --disable-cast5 \
> --disable-exec \
> --disable-photo-viewers \
> --disable-keyserver-helpers \
>
> failed. Thank you.
>
This is your opportunity to contribute to oe-core :) Write a patch that
splits up gnupg recipe into several sub-packages, and send it to the
oe-core mailing list.
Alex
next prev parent reply other threads:[~2017-04-25 13:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 12:57 gnupg strip down star
2017-04-25 13:10 ` Alexander Kanavin [this message]
2017-04-26 5:42 ` Arno Steffens
2017-04-26 10:54 ` Alexander Kanavin
2017-04-26 12:52 ` Arno Steffens
2017-04-26 13:18 ` Alexander Kanavin
2017-04-28 7:31 ` Arno Steffens
2017-04-28 8:35 ` Jussi Kukkonen
2017-04-28 12:30 ` Wold, Saul
2017-05-02 10:06 ` Arno Steffens
2017-05-02 10:38 ` Jussi Kukkonen
2017-05-02 12:14 ` Arno Steffens
2017-04-28 10:06 ` Anders Darander
2017-05-02 9:59 ` Arno Steffens
2017-05-02 13:30 ` Anders Darander
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=29aeb088-beb1-7fa2-b95a-c534f853b374@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=poky@yoctoproject.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.