From: Jaap de Jong <jaap.dejong@nedap.com>
To: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: Re: remove dbg and dev packages
Date: Tue, 20 Mar 2012 11:55:23 +0100 [thread overview]
Message-ID: <4F68621B.4000909@nedap.com> (raw)
In-Reply-To: <4F6756A9.7020106@windriver.com>
On 03/19/2012 04:54 PM, Mark Hatle wrote:
> On 3/16/12 3:54 AM, Jaap de Jong wrote:
>> Hi!
>>
>> is there an option (in local.conf?) to not build (or not add to the
>> repository of) the dbg and dev packages?
> You have to build the dev packages, otherwise you can't (cross) compile the
> software in the development environment.
Clear!
> The dbg packages are optional, but if you disable them then things may or may
> not be stripped and the filesizes on the target may increase. (It's been a
> while since I tried it w/o dbg packages...)
Don't want that.
> Is there a reason why you don't want the dev and dbg packages to be generated?
> They should only be installed onto a target filesystem if you've requested them
> (or a package has a dependency on them). Normal, non-dev, filesystems shouldn't
> be installed any of those components... if they are, there is a packaging bug in
> something.
The only simple reason is to keep the repository's and the Packages*
files smaller.
Thanks for your comments!
prev parent reply other threads:[~2012-03-20 11:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 8:54 remove dbg and dev packages Jaap de Jong
2012-03-16 13:33 ` Henning Heinold
2012-03-19 7:40 ` Jaap de Jong
2012-03-19 15:54 ` Mark Hatle
2012-03-20 10:55 ` Jaap de Jong [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=4F68621B.4000909@nedap.com \
--to=jaap.dejong@nedap.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox