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: Mon, 19 Mar 2012 08:40:21 +0100 [thread overview]
Message-ID: <4F66E2E5.4030108@nedap.com> (raw)
In-Reply-To: <20120316133328.GA13219@mi.fu-berlin.de>
That was my first guess too.
If I remove them from the build/deploy/glibc/ipk/* directories and then
do 'bitbake package-index' that would do the trick?
But I would have to remove them after every package I build...
On 03/16/2012 02:33 PM, Henning Heinold wrote:
> On Fri, Mar 16, 2012 at 09:54:15AM +0100, 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?
>>
>> Thanks!
>> Jaap
>
> Why dont write a shell skript which deletes all dbg and dev packages and calles the opkg index command afterwards?
>
> Bye Henning
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
next prev parent reply other threads:[~2012-03-19 7:49 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 [this message]
2012-03-19 15:54 ` Mark Hatle
2012-03-20 10:55 ` Jaap de Jong
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=4F66E2E5.4030108@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